**UPDATE** JRn 600MB+ shortly after boot up

I rebuilt my machine again.  This time... no Windows updates, no antivirus, nothing... I immediately downloaded the latest installer from Adobe and installed it (Server config with all IIS websites).  JRun is running at 427MB.   This can't be right??

I haven't been reading this thread closely, but is there a specific reason that you think that the JVM shouldn't be that big?  For instance, I have set jvm.config to start jrun with a good chunk of memory right at start up (using -Xms).  Perhaps your's is set that way too?  Have you looked at how much memory the *jvm* has free (vs the size of the jrun.exe *process*)? (If you already covered this then I apologize...) Thanks   Mark

My jvm.config file is unchanged from the initial install (512 max).  When the machine was running on Win XP SP2, I constantly received an error from CF saying cfloop or cfoutput was taking too long.  In both cases, it was referencing files in the Fusebox 5.1 core.  I couldn't load an app that I've been working on nearly 6 months.  I first verified it wasn't code related and then rolled back JVM to 1.5_13/14.  JRun was still eating a ton of memory and consequently, I couldn't get my app to load. My app loads since the latest rebuild.  I'm going to leave it alone as long as I don't experience time out issues again. ________________________________ Sent: Fri 5/16/2008 3:39 PM To: CF-Talk Subject: RE: **UPDATE** JRn 600MB+ shortly after boot up I haven't been reading this thread closely, but is there a specific reason that you think that the JVM shouldn't be that big?  For instance, I have set jvm.config to start jrun with a good chunk of memory right at start up (using -Xms).  Perhaps your's is set that way too?  Have you looked at how much memory the *jvm* has free (vs the size of the jrun.exe *process*)? (If you already covered this then I apologize...) Thanks         Mark

Just curious. Have you tried redownloading ColdFusion on your fresh installs? My jvm.config file is unchanged from the initial install (512 max).  When the machine was running on Win XP SP2, I constantly received an error from CF saying cfloop or cfoutput was taking too long.  In both cases, it was referencing files in the Fusebox 5.1 core.  I couldn't load an app that I've been working on nearly 6 months.  I first verified it wasn't code related and then rolled back JVM to 1.5_13/14.  JRun was still eating a ton of memory and consequently, I couldn't get my app to load. My app loads since the latest rebuild.  I'm going to leave it alone as long as I don't experience time out issues again. ________________________________ Sent: Fri 5/16/2008 3:39 PM To: CF-Talk Subject: RE: **UPDATE** JRn 600MB+ shortly after boot up I haven't been reading this thread closely, but is there a specific reason that you think that the JVM shouldn't be that big?  For instance, I have set jvm.config to start jrun with a good chunk of memory right at start up (using -Xms).  Perhaps your's is set that way too?  Have you looked at how much memory the *jvm* has free (vs the size of the jrun.exe *process*)? (If you already covered this then I apologize...) Thanks         Mark

I don't think what you're seeing is abnormal.  I've got the default JVM configs running as well, and my JRun is running at 522 Megs.  I'm running a the FarCry framework (lots of objects).  I bet if you had a server monitor running, you'd see that used memory is far lower than the memory that it has acquired by the JVM.  This is on a Dell AMD 64x2 with 2 Gigs of RAM laptop.  However, our production servers also exhibit the same behavior.  Right now, my used memory (according to the CF8 monitor) is about 300 megs. Matthew Williams Geodesic GraFX www.geodesicgrafx.com/blog

I have viewed the memory usage in the server monitor.  It was between 375-400MB and would dip periodically only to climb back up where it was after 20-30 seconds. I'm now running ColdBox samples and my own Fusebox app with JRun cruising at 135MB.  I'm not sure what the fix was.  *shrugs* I'm on a E6600 2.4ghz Core 2 Duo w/ 2GB of RAM. I don't think what you're seeing is abnormal.  I've got the default JVM configs running as well, and my JRun is running at 522 Megs.  I'm running a the FarCry framework (lots of objects).  I bet if you had a server monitor running, you'd see that used memory is far lower than the memory that it has acquired by the JVM.  This is on a Dell AMD 64x2 with 2 Gigs of RAM laptop.  However, our production servers also exhibit the same behavior.  Right now, my used memory (according to the CF8 monitor) is about 300 megs. Matthew Williams Geodesic GraFX www.geodesicgrafx.com/blog

Yessir.  I also tried a copy of 8.0.1 I downloaded on April 24th. Just curious. Have you tried redownloading ColdFusion on your fresh installs? My jvm.config file is unchanged from the initial install (512 max). When the machine was running on Win XP SP2, I constantly received an error from CF saying cfloop or cfoutput was taking too long.  In both cases, it was referencing files in the Fusebox 5.1 core.  I couldn't load an app that I've been working on nearly 6 months.  I first verified it wasn't code related and then rolled back JVM to 1.5_13/14.  JRun was still eating a ton of memory and consequently, I couldn't get my app to load. My app loads since the latest rebuild.  I'm going to leave it alone as long as I don't experience time out issues again. ________________________________ Sent: Fri 5/16/2008 3:39 PM To: CF-Talk Subject: RE: **UPDATE** JRn 600MB+ shortly after boot up I haven't been reading this thread closely, but is there a specific reason that you think that the JVM shouldn't be that big?  For instance, I have set jvm.config to start jrun with a good chunk of memory right at start up (using -Xms).  Perhaps your's is set that way too?  Have you looked at how much memory the *jvm* has free (vs the size of the jrun.exe *process*)? (If you already covered this then I apologize...) Thanks         Mark

What makes you think that is not right?  If your Max is set to 512 and you load something as an application, the JVM will determine when to recover memory based on it's own timetable and settings. 427 megs could indeed be appropriate depending on the settings. There are some code snippets on this post that you can use to fiddle with the JVM gc operations - although I would not use them in production. http://www.coldfusionmuse.com/index.cfm/2008/2/12/leaky.heap.jvm If forcing a "stop the world" gc brings your memory back down you are probably worried about it for nothing... Since the JVM will eventually run a full gc on it's own. I rebuilt my machine again.  This time... no Windows updates, no antivirus, nothing... I immediately downloaded the latest installer from Adobe and installed it (Server config with all IIS websites).  JRun is running at 427MB.   This can't be right??

It seems odd to me because Jrun uses significantly less memory on both of my other development machines (my 1GB laptop runs at under 75MB on Vista Ultimate).  The numbers I've been quoting are from Jrun just after boot (idle, no applications loaded) or after only running CFAdmin. Maybe Jrun needs some time to configure itself and requires extra memory when first installed?  Maybe the same can be said for when the machine boots?  I don't know, I'm merely asking. The new box is now running at 165MB. The settings are default (as verified earlier). I'm content with 165MB. What makes you think that is not right?  If your Max is set to 512 and you load something as an application, the JVM will determine when to recover memory based on it's own timetable and settings. 427 megs could indeed be appropriate depending on the settings. There are some code snippets on this post that you can use to fiddle with the JVM gc operations - although I would not use them in production. http://www.coldfusionmuse.com/index.cfm/2008/2/12/leaky.heap.jvm If forcing a "stop the world" gc brings your memory back down you are probably worried about it for nothing... Since the JVM will eventually run a full gc on it's own. I rebuilt my machine again.  This time... no Windows updates, no antivirus, nothing... I immediately downloaded the latest installer from Adobe and installed it (Server config with all IIS websites).  JRun is running at 427MB.   This can't be right??

If you are using Task Manager to judge sizes then be sure to notice the difference between "Mem Usage" and "VM Size"... Mem Usage is the amount of physical ram currently in use by a process, but VM Size is, well, different.  If you have less physical ram on a machine then you may see less Mem Usage but more VM Size (and probably lots of page faults as memory is swapped in and out, seen in Task Manager as "PF Delta").  I always show both Mem Usage and VM Size in Task Manager to get a better picture of actual memory requirements. Thanks   Mark It seems odd to me because Jrun uses significantly less memory on both of my other development machines (my 1GB laptop runs at under 75MB on Vista Ultimate).  The numbers I've been quoting are from Jrun just after boot (idle, no applications loaded) or after only running CFAdmin. Maybe Jrun needs some time to configure itself and requires extra memory when first installed?  Maybe the same can be said for when the machine boots?  I don't know, I'm merely asking. The new box is now running at 165MB. The settings are default (as verified earlier). I'm content with 165MB. What makes you think that is not right?  If your Max is set to 512 and you load something as an application, the JVM will determine when to recover memory based on it's own timetable and settings. 427 megs could indeed be appropriate depending on the settings. There are some code snippets on this post that you can use to fiddle with the JVM gc operations - although I would not use them in production. http://www.coldfusionmuse.com/index.cfm/2008/2/12/leaky.heap.jvm If forcing a "stop the world" gc brings your memory back down you are probably worried about it for nothing... Since the JVM will eventually run a full gc on it's own. I rebuilt my machine again.  This time... no Windows updates, no antivirus, nothing... I immediately downloaded the latest installer from Adobe and installed it (Server config with all IIS websites).  JRun is running at 427MB.   This can't be right??

There was a 100-150MB difference between the Memory Usage reported in CF Admin (which I'm assuming is taping directly into JVM?).  Thanks for the tip with the Task Manager.  I don't seem to have a PID for VM Size? If you are using Task Manager to judge sizes then be sure to notice the difference between "Mem Usage" and "VM Size"... Mem Usage is the amount of physical ram currently in use by a process, but VM Size is, well, different.  If you have less physical ram on a machine then you may see less Mem Usage but more VM Size (and probably lots of page faults as memory is swapped in and out, seen in Task Manager as "PF Delta").  I always show both Mem Usage and VM Size in Task Manager to get a better picture of actual memory requirements. Thanks   Mark It seems odd to me because Jrun uses significantly less memory on both of my other development machines (my 1GB laptop runs at under 75MB on Vista Ultimate).  The numbers I've been quoting are from Jrun just after boot (idle, no applications loaded) or after only running CFAdmin. Maybe Jrun needs some time to configure itself and requires extra memory when first installed?  Maybe the same can be said for when the machine boots?  I don't know, I'm merely asking. The new box is now running at 165MB. The settings are default (as verified earlier). I'm content with 165MB. What makes you think that is not right?  If your Max is set to 512 and you load something as an application, the JVM will determine when to recover memory based on it's own timetable and settings. 427 megs could indeed be appropriate depending on the settings. There are some code snippets on this post that you can use to fiddle with the JVM gc operations - although I would not use them in production. http://www.coldfusionmuse.com/index.cfm/2008/2/12/leaky.heap.jvm If forcing a "stop the world" gc brings your memory back down you are probably worried about it for nothing... Since the JVM will eventually run a full gc on it's own. I rebuilt my machine again.  This time... no Windows updates, no antivirus, nothing... I immediately downloaded the latest installer from Adobe and installed it (Server config with all IIS websites).  JRun is running at 427MB.   This can't be right??