Disable Nagle's algorithm and you should see much better performance. It must not be used on loopback. http://markmail.org/message/rgauuflglwemm24o
On Thu, Jan 20, 2011 at 6:24 AM, George Ciubotaru < george.ciubot...@weedle.com> wrote: > Hello, > > We are in the process of evaluating Cassandra to be used with our product; > I've started with some performance tests but unfortunately I'm getting very > bad results for read operations (around 200 ms per read request which is > much much more than what I'm reading that Cassandra can deliver). > > - I'm using the latest stable Cassandra binaries (Cassandra 0.7) on Windows > - My cluster has 3 nodes (on 3 separate machines), only one seed node and > replication factor of 1 > - I've use batch_mutate to insert around 50,000 keys with an average of 60 > columns per key (no super-column) > - I'm using C# client > - The read operation I've tested was: for a random key get all its columns > (using get_slice) > > I have 2 types of results: > - as expected (very fast, around 1 ms per read request) when the client is > running on one of the 3 machines and is connected with the local machine > - under expectation (200 ms per request) when the client is running on one > of the 3 machines but is connected to one of the other 2 machines (except > local machine). > > It might be configuration issue but I cannot figure it out. > > Any suggestion? > > Thank you, > George
