Are you persisting connections or opening a new one for each operation? Do you understand what deletes actually do internally?
On Mon, Jul 26, 2010 at 12:45 PM, SSam <to_sam...@yahoo.com> wrote: > Thanks for reply > > I am doing very simple test: > I am stressing my webapplication with grinder testing tool. > Number of testing clients is 250, each client just creates/deletes a User > Object( max 500 bytes data). So data is purely WRITE ( I hope Cassandra is > Write Optimized) . > I am running -0.6.3 version, no errors either on cassandra server logs or > my web application server logs. > I have JUST changed listing address and port from default storage-conf.xml > Here is ColumnFamily Defination. > <ColumnFamily Name="Users" CompareWith="UTF8Type"/> > > Anyway I will do testing directly over cassandra bypassing web application. > I will update the forum with my testing results. > > > ________________________________ > From: Bill de hÓra <b...@dehora.net> > To: user@cassandra.apache.org > Sent: Mon, July 26, 2010 3:23:38 PM > Subject: Re: Cassandra Horizontal Scalability > > 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 <p...@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_sam...@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. >> >> >> >> >> >> >> >> > > > >
