On Mon, May 24, 2010 at 7:43 PM, Jonathan Ellis wrote:
> with C# you need to be sure to tell thrift to use client-side
> buffering. http://wiki.apache.org/cassandra/ThriftExamples#C.23 shows
> this (but didn't until recently)
Yes, I am unsing TBufferedTransport. However the high times continues.
with C# you need to be sure to tell thrift to use client-side
buffering. http://wiki.apache.org/cassandra/ThriftExamples#C.23 shows
this (but didn't until recently)
On Mon, May 24, 2010 at 4:09 PM, Carlos Alvarez wrote:
> I have the same issue in my cluster: 0,5% of requests are extremely
> slow
I have the same issue in my cluster: 0,5% of requests are extremely
slow because the time it takes to read the data from the socket.
However in my case it is not related to the load. Actually the
percentage of anomalies drop as the load increases.
On the other hand the nio is actually slow than b
Hi Jonathan,
This sounds a little bit strange, I would expect that NIO server sockets
to be more scalable than regular socket, well I don't have much experience
with tcp programming. What was the scenario you used? The problem I observe
is that most of the requests to Cassandra are quite performa
Because when we tested it, it was slower.
2010/5/21 Даниел Симеонов :
> Hi,
> I have a question about the thrift protocol used to connect to Cassandra,
> I saw in class CassandraDaemon that TServerSocket is being used,
> why TNonblockingServerSocket is not being used? Thank you very much!
> Bes
Hi,
I have a question about the thrift protocol used to connect to Cassandra,
I saw in class CassandraDaemon that TServerSocket is being used,
why TNonblockingServerSocket is not being used? Thank you very much!
Best regards, Daniel.
