On Fri, Jul 16, 2010 at 6:06 PM, Oren Benjamin wrote:
> The first goal was to reproduce the test described on spyced here:
> http://spyced.blogspot.com/2010/01/cassandra-05.html
>
> Using Cassandra 0.6.3, a 4GB/160GB cloud server
> (http://www.rackspacecloud.com/cloud_hosting_products/servers/pr
Hi Jonathan,
The 7k reads/s is very high, could you please make more explain about your
benchmark?
7000 reads/s makes average latency of each read operation only talks
0.143ms. Consider 2 disks in the benchmark, it may be 0.286ms.
But in most random read applications on very large dataset, OS cac
I fact, in my cassandra-0.6.2, I can only get about 40~50 reads/s with
disabled Key/Row cache.
On Sun, Jul 18, 2010 at 1:02 AM, Schubert Zhang wrote:
> Hi Jonathan,
> The 7k reads/s is very high, could you please make more explain about your
> benchmark?
>
> 7000 reads/s makes average latency of
On Sat, Jul 17, 2010 at 12:02 PM, Schubert Zhang wrote:
> Hi Jonathan,
> The 7k reads/s is very high, could you please make more explain about your
> benchmark?
>
> 7000 reads/s makes average latency of each read operation only talks
> 0.143ms. Consider 2 disks in the benchmark, it may be 0.286ms
On Sat, Jul 17, 2010 at 1:31 PM, Brandon Williams wrote:
> Most of the data was hot in either the row/key cache, or in the OS file
> cache. The point was to benchmark Cassandra, not how fast the disk can
> seek.
IIRC we were running w/ the defaults of 200k key cache and no row cache.
--
Jonath
Hi,
I'm seeing an error on one of my nodes after it spends about 2 days
compacting, after which it starts over on the same compaction and
after another 2 days fails again. This causes this node to get horribly
behind on compaction. I've gotten it to clear up a bunch of files by
upping the mini
So still waiting for any sort of answer on this one. The cluster still
refuses to do anything when I bring up new nodes. I shut down all the
new nodes and am waiting. I'm guessing that maybe the old nodes have
some state which needs to get cleared out? Is there anything I can do
at this point?
Not 100% relevant but I found this to be interesting if you're nodes are doing
heavy disk I/O:
http://rackerhacker.com/2008/08/07/reduce-disk-io-for-small-reads-using-memory/
-Chris
On Jul 15, 2010, at 11:47 PM, Peter Schuller wrote:
>> This would require that Cassandra run as root on Linux sy
> Not 100% relevant but I found this to be interesting if you're nodes are
> doing heavy disk I/O:
>
> http://rackerhacker.com/2008/08/07/reduce-disk-io-for-small-reads-using-memory/
There are some pitfalls though, or at least there were the last time I
was tweaking such stuff for a PostgreSQL da
I am trying to load data using contrib/client_only/ClientOnlyExample.java to
write mutations using
StorageProxy.mutate().
When i run the ClientOnlyExample.class with write option against single node
server, it prints as if key has written, and shutting down the message
service, i had to kill the J
10 matches
Mail list logo
