On 01.10.2013 22:09, Michaël Michaud wrote: > Hi Ede, > > A few days ago, I ran OpenJUMP on a windows server with 16G RAM, > and I noticed that it gave nearly 16G to the JVM (I first thought it gave > even more as it showed 17 000 000 000 bytes). > In the script you wrote : > use 100% of ram as default limit (1.124 is a factor to make java64 > really use that much) > Don't understand 1.124, but it seems you really give the maximum > possible memory > to the process.
for some reason java does not interpret values literally when assigned via -Xmx, but always some percentage less. > Can you explain a bit more. Giving 100% ram seems excessive. Moreover, I > thing that > the ram allocated with -xmx excludes the one used by the system to run > the jvm itself. -Xmx is a soft limit telling jre never to use more than that. you can actually set -Xmx to bigger values than ram (incl. page file size) w/o a problem. when there is no memory to reserve anymore jre will throw heap space error anyway. rationale is that desktop software should all memory available. ..ede ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
