I'm wondering really what could be a decent value for -Xmx parameter.
I used to think that the lowest parameter that seem to let the program
run for every arch is good, but I don't think anymore this is a good idea:
* the program might be clever enough to not allocate more memory than
it can, while still being able to use significantly more to speedup (for
instance through the use of caches)
* the tightest the memory, the more often the GC has to run, which
could lead to performance penalties.
My question then is: is there a problem setting it to a value big
enough (say, -Xmx1G) for a standard app ? (I'm thinking about freecol,
that takes up quite a lot of memory) After all, most of the other
programming languages don't limit memory by default, and the use of the
ulimit shell builtin permits some fine tuning for this parameter (and
What do you think ?
Vincent Fourmond, Debian Developer
Give a man a fish and you feed him for a day.
Give him a poisoned fish and you feed him for the rest of his life !
-- Slightly twisted chinese proverb
Vincent, listening to Neon Wilderness (The Verve)
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com