same values for Xmx and Xms: memory extension may be difficult if the OS has not the remaining memory available and may kill the jvm. If the memory is reserved at the start but never used the OS may handle that as well and leave non-used space in swap area (and never swap)

git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@7867 6c8d7289-2bf4-0310-a012-ef5d649a1542

defaults/yacy.init

@@ -615,7 +615,7 @@ cleanup.failedSearchURLtimeout = 86400000
 # if a high performance for large search indexes is wanted, then setting the values to equal number is recommended
 # if YaCy shall be nice in not-only-yacy environments, then the Xms value may be lower
 javastart_Xmx=Xmx600m
-javastart_Xms=Xms180m
+javastart_Xms=Xms600m
 
 # YaCy is able to use RAM copies of database tables. This needs a lot of RAM
 # To switch copying of file tables int RAM on, use this property

htroot/PerformanceQueues_p.java

@@ -86,7 +86,7 @@ public class PerformanceQueues_p {
             if (post.containsKey("Xmx")) {
                 int xmx = post.getInt("Xmx", 500); // default maximum heap size
                 if (OS.isWin32) xmx = Math.min(2000, xmx);
-                int xms = xmx / 4;
+                int xms = xmx; // take all.. if this is not used the os will manage that. if not reserved at the beginning the OS may reject to give away more memory
 	            sb.setConfig("javastart_Xmx", "Xmx" + xmx + "m");
 	            sb.setConfig("javastart_Xms", "Xms" + xms + "m");
 	            prop.put("setStartupCommit", "1");