Share

udt

Tracker: Feature Requests

5 Client/Server performance bottlneck in UDT4 - ID: 1824812
Last Update: Tracker Item Submitted ( veniamin74 )

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.


Veniamin ( veniamin74 ) - 2007-11-02 18:24

5

Open

None

Nobody/Anonymous

None

None

Public


Comments




Log in to comment.

No follow-up comments have been posted.

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.