Hariram wrote:
We are building a Server Application that needs to handle thousands of TCP connections. The usual procedure is to open up a socket for each TCP connection and then construct a read-file-descriptor list and pass it to select(). When select() returns, check for each file descriptor whether it is set in the read-file-descriptor-list. Walking through the list of thousand descriptors to see whether it is ready for read is CPU-consuming.
Instead, is there a way to collect TCP data directly through any other messaging scheme to the User Application?
Is there a way to plumb any module above TCP device (instead of Sockets) so as
to directly send a message to the Application?
Any help?
Look into the extended poll support, it's more efficient than select
and usable in the 10^4 sockets range. If you need 10^5 then that
won't really do either and you'll need to look seriously at
events and async sockets, and I'm fairly sure the latter isn't
implemented yet. Event ports might be.
Cheers,
Jeremy
_______________________________________________
networking-discuss mailing list
[email protected]
