You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by George Ciubotaru <ge...@weedle.com> on 2011/01/20 13:24:27 UTC

Under expectation response time for reads

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

RE: Under expectation response time for reads

Posted by George Ciubotaru <ge...@skillpages.com>.
Hi Miguel,



This indeed solved the problem. The response times are now under 1 ms which  is great.



Thank you once again,

George

From: Miguel Verde [mailto:miguelitovert@gmail.com]
Sent: 20 January 2011 16:46
To: user@cassandra.apache.org
Subject: Re: Under expectation response time for reads

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 <ge...@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


Re: Under expectation response time for reads

Posted by Miguel Verde <mi...@gmail.com>.
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.ciubotaru@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