I actualy run ours with "-memory 64m" on the cmd line.
We have problems with it freezing from time to time. The server freezes always under heavy load, like someone uploading several versions in a row. In this case I log into VNC and wiggle the mouse a bit. Then it continues to serve. I haven't tracked down the problem yet. Ian mumbled something about some stale file handles, but that was about it.
On my to-do list is replacing the awful data.obj dump with something more sensible, like Magma. Our data.obj is now at 6 MB and takes minutes to save. But I'm not sure when I'll get around to that.
- Bert -
Am 15.03.2006 um 19:32 schrieb Ken Causey:
After killing it and starting it again (is there a better way to do that?) it looks more reasonable:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 18484 squeakso 15 0 1026m 18m 2456 S 2.3 1.8 0:09.93 squeakvm -nodisplay SqueakSource-sqf.image
I'll keep an eye on it.
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