Finally I able to configure and run this program on my 3 node cluster.
#python stress.py -n 20 -t 200 -d 172.16.7.76,172.16.7.77,172.16.7.78 -o
read
total,interval_op_rate,avg_latency,elapsed_time
83664,8366,0.0278478825376,10
145478,6181,0.0295496694395,20
177409,3193,0.027055770029,30
This url got simple steps to create cluster and stress testing setup also.
http://www.coreyhulen.org/category/cassandra/
From: SSam
To: user@cassandra.apache.org
Sent: Wed, August 4, 2010 7:02:24 PM
Subject: Re: stress.py
Thanks for the reply,
Issue
Thanks for the reply,
Issue resolved, thift site-packages/thrift/transport/TTransport.py not in
proper path.
I have updated Python PATH , stress.py worked without any issues.
From: Peter Schuller
To: user@cassandra.apache.org
Sent: Wed, August 4, 20
token `('
./stress.py: line 46: `L =
os.path.abspath(__file__).split(os.path.sep)[:-3]'
From: SSam
To: user@cassandra.apache.org
Sent: Wed, August 4, 2010 6:04:49 PM
Subject: Re: stress.py
Peter, Thank you so much for reply.
I am not much familiar with p
File "stress.py", line 36, in
from thrift.transport import TTransport
ImportError: No module named thrift.transport
---
Thanks,
SSam
From: Peter Schuller
To: user@cassandra.apache.org
Sent: Wed, August 4,
Can somebody please give steps to run cassandra stess.py program.
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.
>
not cause the old nodes to speed up.
Also, 1300 reqs/sec is extremely slow, so something else is likely
wrong, as well.
On Mon, Jul 26, 2010 at 8:29 AM, SSam wrote:
>
> From Cassandra Website:
>
> Elastic
>
> Read and write throughput both increase linearly as new machines ar
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 wrote:
>
>From Cassandra Website:
>
> * Elastic
>Read and write
>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
10 matches
Mail list logo