There is of course some additional overhead associated with the TCP protocol
though, which is why it really depends on the reliability of your network
and clients to determine which of the two protocols is ideal for your
environment.
Certainly in the situation being described, where a client is dropping
packets, TCP will likely be the better choice. (Though I'd also want to try
to address the dropped packet problem as well if possible.)
--
Mike Sphar - Sr Systems Administrator - Remedy Corporation
-----Original Message-----
From: Michael Salmon [mailto:Michael.Salmon@uab.ericsson.se]
Sent: Monday, September 23, 2002 3:59 AM
To: toasters@mathworks.com
Subject: Re: Sun Solaris 8 optimal performance with F880
On Thursday, September 19, 2002 11:04:35 PM -0700 Deepak Soneji
sonejideepak@hotmail.com wrote:
+------
| Brian/Tim
|
| Great ! READS are greatly improved upto 12-15 mbps after changing xfersize
| to 8k.
| Any idea about what magic numbers for read/write I should try to achieve
| while tuning ?
|
| Another question, why TCP ?
+-----X8
UDP has no retry mechanism so if you loose any of the 22 packets involved
in a 32k transfer then you need to start again. A powerful server sending
to a weaker client is a good way to ensure that packets are lost. TCP has
mechanism to ensure that packets are not lost and hence works better when
the packet recipient is the weaker partner.
/Michael
--
This space intentionally left non-blank.