Client/Server performance bottlneck in UDT4
Brought to you by:
lilyco
It looks like in the current UDT4 version all child connections, produced by the 'UDT::accept' call, are served by the single in/out worker thread pair.
This causes drammatical perfomance bottleneck for SMP/Multy-core/Multy-way systems.
I would be very glad to see dedicated worker threads serving connections or shared thread pool for all family.