Yeah, do what Kai said and set the minimum heap size to the same as the maximum (means the heap does not have to keep resizing itself as it starts filling up, heap resizing causes full garbage collections before the resize).
The permanent generation size (PermSize) is actually additional to the heap size, As Kai said you don't need to change this unless you have a good reason, but if you need to find out how much of this is actually being used, then turn on garbage collection logging (with the verbose output option). Our site is huge and has bucket loads of classes and it only uses 50MB of the PermSize, we resized ours down to 110MB (depends on how your application is written though). Unless your logs say something like 'out of memory: perm gen space' or something similar you shouldn't need to worry about the PermSize. Once you have thread dumps like you mention, be sure to have a look around for some thread dump parser tools which can summarize the output. In the thread dump, you should be looking for things that keep re-occuring (such as a particular line number in a function), that might indicate the function is slow for some reason, something that occurs only a handful of times would not be something to worry about. You can find out problem threads by taking thread dumps periodicaly (10 seconds apart say), and compare thread dumps for threads that might have been locked or waiting across several dumps (indicating a thread was running for a long time). This link might help you on finding your way through thread dumps: http://kb2.adobe.com/cps/183/tn_18339.html Barry. On Tue, Feb 2, 2010 at 2:09 PM, Andrew Myers <am2...@gmail.com> wrote: > Thanks again Guys. > > I've just watching the FR graphs and I noticed a big 100% spike at 11:54 > which coincided with a long running request. I think I will investigate > this some more... > > Andrew. > > > > > On 2 February 2010 11:52, Kai Koenig <k...@koeni.de> wrote: > >> I think it's jrpp (JRun Proxy Port) - that'd be the case if you're using >> the HTTP-Server >> connector. IF you're using the internal HTTP server, the threads have a >> different identifier >> prefix iirc. >> >> Cheers >> Kai >> >> >> Yup, that's the stuff. >> >> You're looking for threads name jppr* (If I remember correctly), they will >> show you what CF is doing. >> >> Mark >> >> On Tue, Feb 2, 2010 at 11:12 AM, Andrew Myers <am2...@gmail.com> wrote: >> >>> Is this what you guys all mean by the thread dumps? I got this from >>> Resources -> List All Threads -> Stack Trace All >>> >>> >>> -------------------------------------------------------------------------------- >>> Thread Stack TraceTrace Time: 10:46:20.870 02-Feb-2010Thread ID: >>> jms-fifo-1Priority: 5Hashcode: 9107243"jms-fifo-1" prio=5 >>> tid=0x00992fc0 nid=0x13 in Object.wait() [0xa6d01000..0xa6d019c0] >>> at java.lang.Object.wait(Native Method) >>> - waiting on <0xbea19fd0> (a jrun.jms.core.threads.FIFOQueue) >>> at java.lang.Object.wait(Object.java:429) >>> at >>> jrun.jms.core.threads.FIFOQueue.queueHasElements(FIFOQueue.java:45) >>> at jrun.jms.core.threads.FIFOQueue.get(FIFOQueue.java:65) >>> - locked <0xbea19fd0> (a jrun.jms.core.threads.FIFOQueue) >>> at >>> jrun.jms.core.threads.ThreadPoolWorker.runWorker(ThreadPoolWorker.java:91) >>> at >>> jrun.jms.core.threads.ThreadPoolWorker$1.run(ThreadPoolWorker.java:49) >>> at java.lang.Thread.run(Thread.java:534) >>> >>> >>> -------------------------------------------------------------------------------- >>> Thread Stack TraceTrace Time: 10:46:20.877 02-Feb-2010Thread ID: >>> jms-fifo-2Priority: 5Hashcode: 23671183"jms-fifo-2" prio=5 >>> tid=0x008ff8f8 nid=0x14 in Object.wait() [0xa6c01000..0xa6c019c0] >>> at java.lang.Object.wait(Native Method) >>> - waiting on <0xbea1a310> (a jrun.jms.core.threads.FIFOQueue) >>> at java.lang.Object.wait(Object.java:429) >>> at >>> jrun.jms.core.threads.FIFOQueue.queueHasElements(FIFOQueue.java:45) >>> at jrun.jms.core.threads.FIFOQueue.get(FIFOQueue.java:65) >>> - locked <0xbea1a310> (a jrun.jms.core.threads.FIFOQueue) >>> at >>> jrun.jms.core.threads.ThreadPoolWorker.runWorker(ThreadPoolWorker.java:91) >>> at >>> jrun.jms.core.threads.ThreadPoolWorker$1.run(ThreadPoolWorker.java:49) >>> at java.lang.Thread.run(Thread.java:534) >>> >>> >>> -------------------------------------------------------------------------------- >>> Thread Stack TraceTrace Time: 10:46:20.884 02-Feb-2010Thread ID: >>> jms-fifo-3Priority: 5Hashcode: 20239679"jms-fifo-3" prio=5 >>> tid=0x0065bfa0 nid=0x15 in Object.wait() [0xa6b01000..0xa6b019c0] >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "cfaussie" group. >>> To post to this group, send email to cfaus...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> cfaussie+unsubscr...@googlegroups.com<cfaussie%2bunsubscr...@googlegroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/cfaussie?hl=en. >>> >>> >> >> >> -- >> E: mark.man...@gmail.com >> T: http://www.twitter.com/neurotic >> W: www.compoundtheory.com >> >> Hands-on ColdFusion ORM Training @ cf.Objective() 2010 >> www.ColdFusionOrmTraining.com/ >> >> -- >> You received this message because you are subscribed to the Google Groups >> "cfaussie" group. >> To post to this group, send email to cfaus...@googlegroups.com. >> To unsubscribe from this group, send email to >> cfaussie+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/cfaussie?hl=en. >> >> >> _________________________________________________ >> Kai Koenig - Ventego Creative Ltd >> ph: +64 4 476 6781 - mob: +64 21 928 365 / +61 450 132 117 >> web: http://www.ventego-creative.co.nz >> blog: http://www.bloginblack.de >> twitter: http://www.twitter.com/agentK >> >> >> >> >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "cfaussie" group. >> To post to this group, send email to cfaus...@googlegroups.com. >> To unsubscribe from this group, send email to >> cfaussie+unsubscr...@googlegroups.com<cfaussie%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/cfaussie?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "cfaussie" group. > To post to this group, send email to cfaus...@googlegroups.com. > To unsubscribe from this group, send email to > cfaussie+unsubscr...@googlegroups.com<cfaussie%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/cfaussie?hl=en. > -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
