Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of bill@dehora.net designates
 207.7.108.242 as permitted sender)
Subject: Re: Cassandra Horizontal Scalability
From: Bill de =?ISO-8859-1?Q?h=D3ra?= <bill@dehora.net>
Reply-To: bill@dehora.net
To: user@cassandra.apache.org
In-Reply-To: <428803.96244.qm@web65709.mail.ac4.yahoo.com>
References: <387977.33632.qm@web65713.mail.ac4.yahoo.com>
	 <AANLkTikumvpbDTO0wo9Wm7Sbk2qvWehk3GDQk=fJC+=r@mail.gmail.com>
	 <428803.96244.qm@web65709.mail.ac4.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 26 Jul 2010 20:23:38 +0100
Message-ID: <1280172218.5487.18.camel@dehora-laptop>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

Initially, try running stress.py against your servers. That will help
eliminate pelops as the issue.

Also, some more detail on your setup wouldn't hurt, 1300 anything a
second is low. 

Is the TPS reads or writes, or a mix? 

What's the column family structure? 

Is the data large (eg are you writing binary files)?

How many client processes are you running? 

What are the server configurations?

How much data are nodes carrying? 

What does the output of ./nodetool cfstats say?

What version of cassandra are you running?

Are there errors in the server logs?

Bill

On Mon, 2010-07-26 at 09:26 -0700, SSam wrote:
> 
> I have fully separated gigabit  private subnet. 
> I am using  pelops cassandra java client with 150 client pool. 

> 
> 
> 
> ______________________________________________________________________
> From: Paul Prescod <paul@prescod.net>
> To: user@cassandra.apache.org
> Sent: Mon, July 26, 2010 12:21:06 PM
> Subject: Re: Cassandra Horizontal Scalability
> 
> There are a lot of variables that go into a proper benchmark. The
> bottleneck could be in many different places.
> 
> 
> How many client threads are you using? What kind of network? 
> 
> On Mon, Jul 26, 2010 at 8:29 AM, SSam <to_sam007@yahoo.com> wrote:
>         
>         From Cassandra Website:
>               * Elastic 
>                 
>                 Read and write throughput both increase linearly as
>                 new machines are added, with no downtime or
>                 interruption to applications. 
>                 
>         
>         I am testing TPS with Cassandra cluster.  
>         Initially I have tested with one node cluster , got 1300
>         TPS,   
>         added another node and I got 1200 TPS with 2 node cluster.  
>         TPS supposed to increase  with every additional node.  I am
>         not sure what I am doing wrong?   Any suggestions on Cassandra
>         Scalability? 
>         
>         Thanks,
>         Sam. 
>         
>         
>         
>         
>         
> 
> 
>