Menu

#4 Client/Server performance bottlneck in UDT4

open
nobody
None
5
2013-01-28
2007-11-02
Veniamin
No

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.

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.