Out of interest can you quantify the throughput reduction ? It looks like less
than 10%.
Nice to see it roughly correspond to SEDA throughput :)
> Check how many concurrent real requests you have vs size of thread pools.
Did the change the defaults for the hsha settings below?
How many concurre
Check how many concurrent real requests you have vs size of thread pools.
Regards,
Terje
On 30 Oct 2012, at 13:28, Peter Bailis wrote:
>> I'm using YCSB on EC2 with one m1.large instance to drive client load
>
> To add, I don't believe this is due to YCSB. I've done a fair bit of
> client-sid
>
> I'm using YCSB on EC2 with one m1.large instance to drive client load
To add, I don't believe this is due to YCSB. I've done a fair bit of
client-side profiling and neither client CPU or NIC (or server NIC) are
bottlenecks.
I'll also add that this dataset fits in memory.
Thanks!
Peter
Hi,
I'm currently benchmarking Cassandra and have encountered some interesting
behavior. As I increase the number of client threads (and connections),
latency increases as expected but, at some point, throughput actually
decreases.
I've seen a few posts about this online, with no clear resolution
