PHWinfo - Afficher un message - Re: For performance, one socket or two with dedicated send/receive?

06/03/2006, 15h12

Well, the application isn't heavy bidirectional, it will be really
heavy in one direction, and light in the other. I want to guarantee
that the light direction doesn't suffer from any starvation if the
other direction is under heavy load.

I'm not concerned about the ACKs, I'm not sure if I should be.

So, would having two dedicated TCP connections (4 ports total - 2
endpoints on each side) in my application, 1 for sending, 1 for
receiving, would improve performance and mitigate starvation given this
context? From what you've said so far, it doesn't sound like it.

06/03/2006, 15h12	#3
Druid Messages: n/a Hébergeur:	Re: For performance, one socket or two with dedicated send/receive? Well, the application isn't heavy bidirectional, it will be really heavy in one direction, and light in the other. I want to guarantee that the light direction doesn't suffer from any starvation if the other direction is under heavy load. I'm not concerned about the ACKs, I'm not sure if I should be. So, would having two dedicated TCP connections (4 ports total - 2 endpoints on each side) in my application, 1 for sending, 1 for receiving, would improve performance and mitigate starvation given this context? From what you've said so far, it doesn't sound like it.