Thanks all for the help.
I ran the traffic over the weekend surprisingly, my heap was doing OK
(around 5.7G of 8G) but GC activity went nuts and dropped the throughput. I
will probably increase the number of nodes.
The other interesting thing I noticed was that there were some objects with
finaliz
I believe you should roll out more nodes as a temporary fix to your problem,
400GB on all nodes means (as correctly mentioned in other mails of this thread)
you are spending more time on GC. Check out the second comment in this link by
Aaron Morton, he says the more than 300GB can be problematic
One or more of these might be effective depending on your particular usage
- remove data (rows especially)
- add nodes
- add ram (has limitations)
- reduce bloom filter space used by increasing fp chance
- reduce row and key cache sizes
- increase index sample ratio
- reduce compaction concurrency
You are right, it looks like I am doing a lot of GC. Is there any
short-term solution for this other than bumping up the heap ? because, even
if I increase the heap I will run into the same issue. Only the time before
I hit OOM will be lengthened.
It will be while before we go to latest and greate
Sounds like you're spending all your time in GC, which you can verify
by checking what GCInspector and StatusLogger say in the log.
Fix is increase your heap size or upgrade to 1.2:
http://www.datastax.com/dev/blog/performance-improvements-in-cassandra-1-2
On Wed, May 29, 2013 at 11:32 PM, srmore
Hello,
I am observing that my performance is drastically decreasing when my data
size grows. I have a 3 node cluster with 64 GB of ram and my data size is
around 400GB on all the nodes. I also see that when I re-start Cassandra
the performance goes back to normal and then again starts decreasing af
