Re: [Slashcode-general] performance/memory issues [was: Problems...] (fwd)

[Nathan V. <na...@th...>]

Delrin wrote to me only but I thought I'd share it with the whole list...

---------- Forwarded message ----------
Date: Wed, 06 Jun 2001 10:14:46 -0400
From: Delrin Kenro <del...@ho...>
To: na...@th...
Subject: Re: [Slashcode-general] performance/memory issues [was:
    Problems...]


I had the exact same problems. This is due to the size of the "memory
footprint" used by slashd, and even more importantly. Apache/mod_perl. I
have a P3 500 w/128MB RAM, and redhat 7.0. I would say that this
configuration is BARELY suited to running slash, but it can work if you
have a low concurrency on your site.

Definately keep your min/max servers very low, don't bother with
maxrequestsperchild, it won't help. Use ::SizeLimit if you can, I use it,
though it doesn't work very well.

MinSpareServers 1
MaxSpareServers 5

PerlFixupHandler Apache::SizeLimit

StartServers 1

Here's some of the settings I have that work quite well. BUT, also, make
sure your system is dedicated for slash. What I mean by this is that
there are no unnecessary processes running that take up memory.
Especially things like Xfree. If you have a dual boot or something, set
up a runlevel to work just for slash, that's what I did, and I have
another to use Xfree.

The processes still get pretty huge, and consume more and more memory. At
one time, my apache was taking 33MB of RAM for each process! My machine
started to swap after a few days, and would just die.

Now here's what it looks like.

PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND

2967 nobody     0   0 10020 5172  4976 S     0.0  4.0   0:00 httpd

and for slash

654 nobody     0   0 14028  13M  1744 S     0.0 10.9   0:44 slashd



10MB and 14MB respectably. You can imagine if I was running say 10-12
apache servers. :)