Still seems MEM.
However it's hard to convince that constantly writing(even great amount
of data) needs so much MEM(16GB). The process is quite simple,
input_data - memtable - flush to disk
right? What does cassandra need so much MEM for?
Thanks!
?? 2010-06-02 16:24 +0800??lwl??
No.
: [***SPAM*** ] Re: writing speed test
: Wed, 2 Jun 2010 10:44:52 +0200
Since this thread has now gone on for a while...
As far as I can tell you never specify the characteristics of your
writes. Evaluating expected write throughput in terms of MB/s to
disk is pretty impossible if one does
Thanks lwl.
Then is there anyway of tuning this, faster flush to disk or else?
Cheers,
Kevin
?? 2010-06-02 09:57 +0800??lwl??
MEM: almost 100% (16GB)
-
maybe this is the bottleneck.
writing concerns Memtable and SSTable in memory.
?? 2010??6??2?? 9:48??Shuai
is all the 4 servers' MEM almost 100%?
在 2010年6月2日 上午10:12，Shuai Yuan yuansh...@supertool.net.cn写道：
Thanks lwl.
Then is there anyway of tuning this, faster flush to disk or else?
Cheers,
Kevin
在 2010-06-02三的 09:57 +0800，lwl写道：
MEM: almost 100% (16GB)
-
maybe this
?? 2010-06-02 10:37 +0800??lwl??
is all the 4 servers' MEM almost 100%?
Yes
?? 2010??6??2?? 10:12??Shuai Yuan yuansh...@supertool.net.cn??
Thanks lwl.
Then is there anyway of tuning this, faster flush to disk or
else?
