<d1b2>
<Qyriad> Iirc the tl;dr was use python-libusb1 with async transfers instead of PyUSB, and benchmark to make sure any Python data-parsing code isn't getting in the way of the USB transfers
<d1b2>
<davoid> thx
<d1b2>
<davoid> because cdc was slower? or just to get a separate descriptor as you own both sides?
<d1b2>
<Qyriad> idk, we weren't there for when it was implemented, but I'd assume it was just because it was simpler
<d1b2>
<Qyriad> Didn't have to go and correctly implement a proper USB class; they just made a bulk endpoint that sporked raw data any time it was asked
<d1b2>
<Qyriad> I don't know enough about CDC to know what overhead it has, so I don't know how helpful these results will be for you, but if you're having performance issues then switching to python-libusb1 and async transfers is a good bet
<d1b2>
<davoid> will try and mimic that implementation
<d1b2>
<davoid> i was mainly interested if several bulk endpoint was used to trick the OS of filling the outgoing phy buffers in a more efficient way
<d1b2>
<Holonium> Any chance that a Glasgow ordered June 2021 will arrive before August this year under current conditions?