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

03/03/2006, 01h22

In article <1141336756.033668.74080@t39g2000cwt.googlegroups. com>,
"Druid" <mattdruid@gmail.com> wrote:

> A TCP connection can send and receive over the same connection, but
> is there a benifit to creating two TCP connections? I was thinking of
> using one specifically for sending, and one specifically for receiving.
> In what cases, if any, would you want to use two? This might be a
> newbie question, but I've been unable to find an answer about it yet.

I don't think there would be a significant benefit. If you use one
connection, ACKs can be piggy-backed on data segments, so you may get
slightly better performance this way.

--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***

03/03/2006, 01h22	#1
Barry Margolin Messages: n/a Hébergeur:	Re: For performance, one socket or two with dedicated send/receive? In article <1141336756.033668.74080@t39g2000cwt.googlegroups. com>, "Druid" <mattdruid@gmail.com> wrote: > A TCP connection can send and receive over the same connection, but > is there a benifit to creating two TCP connections? I was thinking of > using one specifically for sending, and one specifically for receiving. > In what cases, if any, would you want to use two? This might be a > newbie question, but I've been unable to find an answer about it yet. I don't think there would be a significant benefit. If you use one connection, ACKs can be piggy-backed on data segments, so you may get slightly better performance this way. -- Barry Margolin, barmar@alum.mit.edu Arlington, MA * PLEASE post questions in newsgroups, not directly to me * * PLEASE don't copy me on replies, I'll read them in the group *