byzhang / terrastore

Automatically exported from code.google.com/p/terrastore
Other
0 stars 0 forks source link

Garbage collector server side #184

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Dear Sergio,
 I'm testing the terrastore cluster. I have configured a minimal cluster with only one server e only one master
 I try to put 150000 objects (every one have a size of 1M) into the terrastore cluster. 
Theese objects are uploaded by one client in sequentially manner.
I'm monitoring the server activity but the server couldn't remove the heap 
memory space. The garbage collector don't removes the allocated memory and 
after 4k objects uploaded, the server crash.
Can i press the garbage collector activities?
What is the optimal configuration for a large number of objects?

Thanks in advance,
Roberto

Original issue reported on code.google.com by robci...@gmail.com on 14 Oct 2011 at 9:41

GoogleCodeExporter commented 9 years ago
Hi Roberto,

sorry for the late reply, I've been away until a few days ago.

First, having your server heap configuration would greatly help in debugging 
the problem, as well as the server and garbage collector logs: just enable the 
latter with the "-verbose:gc" startup option.
Also, tuning the cache manager configuration in the terracotta xml file may 
help, more specifically...

Percentage of objects to evict and make available for GC:

        <property name="l2.cachemanager.percentageToEvict" value="25"/>

First threshold upon which firing eviction:

        <property name="l2.cachemanager.threshold" value="50"/>

Second threshold upon which firing eviction:

        <property name="l2.cachemanager.criticalThreshold" value="70"/>

Try raising the first and/or lowering the other ones.

Let us know.

Original comment by sergio.b...@gmail.com on 3 Nov 2011 at 8:24