This question is probably better served for the users list, not the dev list.
JVM tuning is mainly based on the application profile. For example, if you have a lot of columns that have a decent amount of data in them, the node will require more memory to do compactions. But if you give it to much memory, say 6Gigs, GC's could take a to long and slow down your throughput considerably. It's really about finding the sweet spot for your particular application. Start with 1G max and work you way up if you need to. Some people prefer more nodes with smaller heaps rather than fewer nodes with larger heaps. -Mark 2010/4/7 Bingbing Liu <rucb...@gmail.com> > such as : > the XMX for jvm ? -the default XMX is 1G > the RpcTimeoutInMills? > ConcurrentReads？ > ConcurrentWrites？ > > is there any rules ? such as "when the xmx is set to *% of the size of the > physical memory , the performance is the best" > > > > > 2010-04-07 > > > > Bingbing Liu >
