Thanks Ken, setting up tightvnc to view the image directly sounds like a great idea.
- Doug
On Mon, 20 Mar 2006 15:53:41 -0600, "Ken Causey" ken@kencausey.com said:
As of today it has grown to 149 MB of memory (resident set size). I'm going to set up tightvnc so I can check the image more directly. I hope that's OK with you. I will let you know the password once I have set it up.
Ken
On Wed, 2006-03-15 at 13:18 -0500, Doug Way wrote:
I'm pretty sure it shouldn't be using that much memory. It may be that cruft has accumulated in the image as it's been running for a long time.
You could try restarting the process, and see how much memory it says it uses after the restart?
- Doug
On Wed, 15 Mar 2006 12:13:02 -0600, "Ken Causey" ken@kencausey.com said:
I'm wondering if the current usage level (primarily memory, but also CPU) that I'm seeing for source.squeakfoundation.org are to be expected.
Should it be using 320MB of memory? Note that this compares to approximately 40MB for all other Squeak server processes running.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 12479 squeakso 15 0 1026m 320m 2456 S 15.3 32.1 1837:28 squeakvm
Ken