The growth is in the perm space. It's part of the JRun JVM process memory (reported by Task Manager) but not part of the JVM heap (reported by Server Monitor). It's not exactly external to CF - it's part of how CF (or any Java app) works. CF creates a lot of classes to do what it does, which all use perm space.
On Fri, Mar 21, 2008 at 6:13 AM, Alex DeMarco <[EMAIL PROTECTED]> wrote: > >Server monitor is reporting the used heap space but not the perm > >space. As time goes on more and more classes have been compiled and > >are being stored in the perm space. Hotspot-optimized code also lives > >in the perm space, which also accumulates over time. > > > >http://www.javaperformancetuning.com/news/qotm043.shtml > > > >On Fri, Mar 21, 2008 at 12:55 AM, Alex DeMarco <[EMAIL PROTECTED]> wrote: > >> > > So if the internal monitor is not showing the memory growth but Windows Task > manager is then is the growth external to CFMX? But something else in the > Jrun instance? > > - Alex > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:301712 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
