Revision: 3727
http://bigdata.svn.sourceforge.net/bigdata/?rev=3727&view=rev
Author: btmurphy
Date: 2010-10-04 20:53:59 +0000 (Mon, 04 Oct 2010)
Log Message:
-----------
[branch dev-btm]: hand-merged changeset 3528 from trunk --> dev-btm
Modified Paths:
--------------
branches/dev-btm/src/resources/config/bigdataCluster.config
branches/dev-btm/src/resources/config/bigdataCluster16.config
branches/dev-btm/src/resources/config/bigdataStandalone.config
Modified: branches/dev-btm/src/resources/config/bigdataCluster.config
===================================================================
--- branches/dev-btm/src/resources/config/bigdataCluster.config 2010-10-04 20:44:17 UTC (rev 3726)
+++ branches/dev-btm/src/resources/config/bigdataCluster.config 2010-10-04 20:53:59 UTC (rev 3727)
@@ -768,10 +768,11 @@
* have for your applications!
*/
"-Xmx1600m",// was 800
- /* Optionally, grab all/most of the max heap at once. This makes sense for
- * DS but is less necessary for other bigdata services.
+ /* Pre-allocation of the DS heap is no longer recommended.
+ *
+ * See https://sourceforge.net/apps/trac/bigdata/ticket/157
+ "-Xms800m",
*/
- "-Xms800m", // 1/2 of the max heap is a good value.
/*
* This option will keep the JVM "alive" even when it is memory starved
* but perform of a memory starved JVM is terrible.
Modified: branches/dev-btm/src/resources/config/bigdataCluster16.config
===================================================================
--- branches/dev-btm/src/resources/config/bigdataCluster16.config 2010-10-04 20:44:17 UTC (rev 3726)
+++ branches/dev-btm/src/resources/config/bigdataCluster16.config 2010-10-04 20:53:59 UTC (rev 3727)
@@ -813,12 +813,11 @@
* http://blogs.msdn.com/ntdebugging/archive/2009/02/06/microsoft-windows-dynamic-cache-service.aspx
*/
"-Xmx9G", // Note: out of 32 available!
- /* Optionally, grab all/most of the max heap at once. This makes sense for
- * DS, but is less necessary for other bigdata services. If the machine is
- * dedicated to the DataService then use the maximum heap. Otherwise 1/2 of
- * the maximum heap is a good value.
- */
+ /* Pre-allocation of the DS heap is no longer recommended.
+ *
+ * See https://sourceforge.net/apps/trac/bigdata/ticket/157
"-Xms9G",
+ */
/*
* FIXME This might not be required, so that should be tested.
* However, you don't want the JVM to just die if it is being
Modified: branches/dev-btm/src/resources/config/bigdataStandalone.config
===================================================================
--- branches/dev-btm/src/resources/config/bigdataStandalone.config 2010-10-04 20:44:17 UTC (rev 3726)
+++ branches/dev-btm/src/resources/config/bigdataStandalone.config 2010-10-04 20:53:59 UTC (rev 3727)
@@ -781,10 +781,11 @@
* have for your applications!
*/
"-Xmx4g",// was 800
- /* Optionally, grab all/most of the max heap at once. This makes sense for
- * DS but is less necessary for other bigdata services.
+ /* Pre-allocation of the DS heap is no longer recommended.
+ *
+ * See https://sourceforge.net/apps/trac/bigdata/ticket/157
+ "-Xms2G",
*/
- "-Xms2G", // 1/2 of the max heap is a good value.
/*
* This option will keep the JVM "alive" even when it is memory starved
* but perform of a memory starved JVM is terrible.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
