G
Guest
Hi,
I'm working on a client/server application.
In the current design, a new thread will be spawn, both on server and
client side,
to process every packet received.
As both client and server and client applications will be receiving
thousands of
of packets in any single session, there would be thousands of threads
created
to process the packets and then destroyed. I read in one of the
microsofts article
that this is an extra overhead and hence not recommended.
On the other hand, if we use thread pool, there would be only 25 threads
available to process the thousands of packets received.
In this scenario, what would be the better choise between a thread for a
packet,
thread pool.
kindly let me know. If you need any more information do not hesitate to
contact
me.
Cheers,
Naveen.
I'm working on a client/server application.
In the current design, a new thread will be spawn, both on server and
client side,
to process every packet received.
As both client and server and client applications will be receiving
thousands of
of packets in any single session, there would be thousands of threads
created
to process the packets and then destroyed. I read in one of the
microsofts article
that this is an extra overhead and hence not recommended.
On the other hand, if we use thread pool, there would be only 25 threads
available to process the thousands of packets received.
In this scenario, what would be the better choise between a thread for a
packet,
thread pool.
kindly let me know. If you need any more information do not hesitate to
contact
me.
Cheers,
Naveen.