Also, which client language are you using? It's possible that you may be using a TSocket without buffering -- depending upon the language you probably want to wrap the Tsocket in a TBufferedTransport to avoid lots of syscalls to incrementally read data off the socket -- rather than out of a decently sized buffer in application space.
-----Original Message----- From: David Reiss [mailto:[EMAIL PROTECTED] Sent: Thursday, June 12, 2008 11:05 AM To: [email protected] Subject: Re: strange network latency... something about TSocket? Dropped TCP packets maybe? I've heard the retransmit timeout is about 200 ms. I think you can get retransmit counts from the kernel with netstat. --David Erik Frey wrote: > Hi All, > > I'm trying to use thrift in a low-latency scenario. Even at low loads > (just a few hundred requests a second) occasionally (a few times a > second) a round trip from the client to the server takes 250 > milliseconds. I'm using the default TSocket settings, so it's > probably not nodelay, and I'm using TNonblockingServer, using > 20080411p1 from the web site. > > Just curious if anyone's seen this before? > > Interestingly, when I measure the round trip time on the server end > (inserting timing code before and after processor->process(in, out)), > it's what I would expect. The delay seems to be on the client side. > > Erik >
