-
Notifications
You must be signed in to change notification settings - Fork 0
Notes
sergio contrino edited this page Dec 9, 2013
·
27 revisions
-
[InterMine public doc] (http://intermine.readthedocs.org/en/latest/system-requirements/software/postgres/postgres/)
-
[performance book] (https://www.packtpub.com/article/server-configuration-tuning-postgresql)
- [Java resources] (http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html)
- [ANT_OPTS] (http://javahowto.blogspot.co.uk/2006/06/6-common-errors-in-setting-java-heap.html)
| XX:SoftRefLRUPolicyMSPerMB | Starting with 1.3.1, softly reachable objects will remain alive for some amount of time after the last time they were referenced. The default value is one second of lifetime per free megabyte in the heap. This value can be adjusted using the -XX:SoftRefLRUPolicyMSPerMB flag, which accepts integer values representing milliseconds. For example, to change the value from one second to 2.5 seconds, use this flag: -XX:SoftRefLRUPolicyMSPerMB=2500 The Java HotSpot Server VM uses the maximum possible heap size (as set with the -Xmx option) to calculate free space remaining. The Java Hotspot Client VM uses the current heap size to calculate the free space. This means that the general tendency is for the Server VM to grow the heap rather than flush soft references, and -Xmx therefore has a significant effect on when soft references are garbage collected. On the other hand, the Client VM will have a greater tendency to flush soft references rather than grow the heap. The behavior described above is true for 1.3.1 through Java SE 6 versions of the Java HotSpot VMs. This behavior is not part of the VM specification, however, and is subject to change in future releases. Likewise the -XX:SoftRefLRUPolicyMSPerMB flag is not guaranteed to be present in any given release. |