Date: Wed, 31 May 2006 11:14:21 +0400 From: Artem Gr <artem@bizlink.ru> To: freebsd-java@freebsd.org Cc: Vadim Goncharov <vadimnuclight@tpu.ru>, Kurt Miller <kurt@intricatesoftware.com> Subject: Re: diablo 1.5 died after 5 day uptime Message-ID: <447D424D.3020703@bizlink.ru> In-Reply-To: <200605301107.05985.kurt@intricatesoftware.com> References: <ops931hxox17d6mn@nuclight.avtf.net> <200605261307.06671.kurt@intricatesoftware.com> <ops955inu24fjv08@nuclight.avtf.net> <200605301107.05985.kurt@intricatesoftware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> high. Note that the jvm uses more memory then is controlled >>> by the -Xmx arg. You need to leave some head room for that if >>> your going to be setting your limits lower. >> OK, thanx. Is that overhead big? > > It varies depending on what your application does. The JVM itself uses memory and there is additional area for JIT-compiled Java classes and for the young generation of the GC (can control that with -Xmn). > Overall, > I think you will find there is plenty of information on the > web about how to tune memory usage of the jvm. Like http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?447D424D.3020703>