On Fri, Dec 3, 2010 at 12:51 PM, Brook Davies <cft...@logiforms.com> wrote: > > 1. I understand that setting -Xms1024m -Xmx1024m should immediately > allocate that amount of ram to the JVM. So why does the taskManager report > the memory usage at 300 megs (prior to the event)?
I think the answer to this one is that JRun grabs the full 1024MB but Task Manager is reporting only what JRun tells you it is using - so it's not actually reporting allocated memory but used memory. > 2. If a bunch of requests cause memory usage to spike and then those > requests die off, should seefusion show memory usage at 90% because thats > whats allocated to the JVM and now 'claimed'? So would that be a normal > operating condition? SeeFusion will show 90% usage until the memory used by those threads is garbage collected. Thus, until garbage collection, Task MAnager would also report the higher memory usage. > 3. What would cause the memory to immediately climb back up after a > full GC after 'something' happened but not climb after the service is > restarted? This one I can't answer = ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:339763 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
