Hi Brandon,
i've recoded my client (using threads). Now i'am getting round about 240
inserts per second (i think the bottleneck is know the virtualized hardware -->
single cpu). The stress.py script gives about 50 inserts/sec.
I'll test cassandra on real hw to see if it's perform better under a
On Thu, Mar 18, 2010 at 1:22 PM, Martin Probst (RobHost Support) <
supp...@robhost.de> wrote:
> Hi Tom,
>
> no we're not using a connection pool, only pure java on cmd.
>
> Cheers,
> Martin
>
>
The second graph here is relevant:
http://spyced.blogspot.com/2010/01/cassandra-05.html
Rather than cre
Hi Tom,
no we're not using a connection pool, only pure java on cmd.
Cheers,
Martin
Am 18.03.2010 um 19:18 schrieb Tom Chen:
> Hi Martin,
>
> Are you using a connection pool? I have been able to get about a 1000+
> inserts with java code on one cassandra node with small values(100 bytes).
>
How did you mean that, are there some config adjustments, or did you mean the
inserting client?
Martin
Am 18.03.2010 um 19:18 schrieb Jonathan Ellis:
> Perhaps you're only inserting with a single thread?
>
> On Thu, Mar 18, 2010 at 1:03 PM, Martin Probst (RobHost Support)
> wrote:
>> Hi,
>>
Hi Roger,
we've only adjusted the names for the keyspaces and the columnfamilies. This is
the second perl benchmark code, which switches the node after 100 datasets:
#!/usr/bin/perl
use strict;
use warnings;
use Data::Dumper qw( Dumper );
use Net::Cassandra;
my $host1 = "localhost";
my $host
Hi Martin,
Are you using a connection pool? I have been able to get about a 1000+
inserts with java code on one cassandra node with small values(100 bytes).
Tom
On Thu, Mar 18, 2010 at 11:08 AM, Roger Schildmeijer wrote:
> Yes, 30 writes / s sounds a little bit poor.
>
> Maybe you could show
Perhaps you're only inserting with a single thread?
On Thu, Mar 18, 2010 at 1:03 PM, Martin Probst (RobHost Support)
wrote:
> Hi,
>
> we've tested the write performance on a single and dual node cluster and the
> results are strangely poor. We've got about 30 inserts per second which seems
> a
Yes, 30 writes / s sounds a little bit poor.
Maybe you could show your benchmark code? And what adjustments had to be done
to the CF?
// Roger
On 18 mar 2010, at 19.03em, Martin Probst (RobHost Support) wrote:
> Hi,
>
> we've tested the write performance on a single and dual node cluster an
Hi,
we've tested the write performance on a single and dual node cluster and the
results are strangely poor. We've got about 30 inserts per second which seems a
little bit slow?! The strange about is, that the node's we've used (single-cpu,
3gb ram, single disk) got a load of 0.02-0.05 while th
