Are you using TSocket in the client?. If yes, use TbufferedTransport instead.
Carlos On 4/29/10, Viktor Jevdokimov <viktor.jevdoki...@adform.com> wrote: > Thrift C# sources, thrift generated Cassandra sources, test app built with > C#. Simple connect/write/read operations. No pooling or anything else. > > From: Heath Oderman [mailto:he...@526valley.com] > Sent: Thursday, April 29, 2010 2:17 PM > To: user@cassandra.apache.org > Subject: Re: Cassandra on Windows network latency > > I learned the hard way, that running py_stress in the src/contrib directory > is a great way to test what kind of speeds you are really getting. > > What tools / client are you using to test to get the 200ms number? > > stu > On Thu, Apr 29, 2010 at 7:12 AM, Viktor Jevdokimov > <viktor.jevdoki...@adform.com<mailto:viktor.jevdoki...@adform.com>> wrote: > Hi all, > > We have installed Cassandra on Windows and found that with any number of > Cassandra (single, or 3 node cluster) on Windows Vista or Windows Server > 2008, 32 or 64 bit, with any load or number of requests we, have: > > When client and server are on the same machine, connect/read/write latencies > ~0-1ms > When client on another machine, same network, on the same switch, connection > latency 0-1ms (as a ping), read/write latencies >=200ms. > > What causes 200ms latency accessing Cassandra on Windows through network? > Does anybody experience such behavior? > > Cassandra 0.6.1 > Java SE 6 u20 > > > Best regards, > Viktor > > > -- Sent from my mobile device Tal vez hubo un error en la grafía. O en la articulación del Sacro Nombre.
