@chris. Thanks. I wil keep you update if I find something
@Joe. I am not telling this is a bad number. I am just telling this is
still not enough for us ( in order to limit the number of nodes) ;o)
If I look at the last bench, version 0.6.2 is around 13000w/s
I should/would be able to reach 1000
> @Chris, Did you get any bench you could share with us?
We're still working on it. It's a lower priority task so it will take a
while to finish. So far we've run on all the AWS data centers in the US
and used several different setups. We also did a test on Rackspace with
one setup and some whi
On Jun 18, 2010, at 6:39 PM, Olivier Mallassi wrote:
> and I did not see any improvements (Cassandra stays around 7000 W/sec).
It's a brave new world where N+1 scaling with 7,000 writes per second per node
is considered suboptimal performance.
--Joe
I tried the following :
- always one cassandra node on one EC2 m.large instance. two other m.large
instance, I run 4 stress.py (50 thread each, 2 stress.py on each instance)
- RAID0 EBS for data and ephemeral EBS (/dev/sda1 partition) for commit log.
- -Xmx4G
and I did not see any improvements (Ca
On Fri, Jun 18, 2010 at 8:00 AM, Olivier Mallassi wrote:
> I use the default conf settings (Xmx 1G, concurrentwrite 32...) except for
> commitlog and DataFileDirectory : I have a raid0 EBS for commit log and
> another raid0 EBS for data.
> I can't get through 7500 write/sec (when launching 4 stres
Hi all,
@Chris, Did you get any bench you could share with us?
I am running the same kind of test on EC2 (m.large instances) :
- one VM for stress.py (can be launched several times)
- another VM for a unique cassandra node
I use the default conf settings (Xmx 1G, concurrentwrite 32...) except f
On Fri, May 28, 2010 at 3:48 PM, Mark Greene wrote:
> First thing I would do is stripe your EBS volumes. I've seen blogs that say
> this helps and blogs that say it's fairly marginal.
just to point out: another option is to stripe the ephemeral drives
(if using instances > small)
First thing I would do is stripe your EBS volumes. I've seen blogs that say
this helps and blogs that say it's fairly marginal. (You may want to try
rackspace cloud as they're local storage is much faster.)
Second, I would start out with N=2 and set W=1 and R=1. That will mirror
your data across t
Mark Greene writes:
> If you give us an objective of the test that will help. Trying to get max
> write throughput? Read throughput? Weak consistency?
I would like reading to be as fast as I can get. My real-world problem
is write heavy, but the latency requirements are minimal on that side.
If
If you give us an objective of the test that will help. Trying to get max
write throughput? Read throughput? Weak consistency?
On Thu, May 27, 2010 at 8:48 PM, Chris Dean wrote:
> I'm interested in performing some simple performance tests on EC2. I
> was thinking of using py_stress and Cassandr
I'm interested in performing some simple performance tests on EC2. I
was thinking of using py_stress and Cassandra deployed on 3 servers with
one separate machine to run py_stress.
Are there any particular configuration settings I should use? I was
planning on changing the JVM heap size to refle
11 matches
Mail list logo
