|
From: Nathan V. <na...@th...> - 2001-06-05 20:08:53
|
We have had similar issues with a box that only has 128 mb of RAM. Try
these things:
1. buy more memory!
2. in httpd.conf,
turn Timeout way down (e.g. 60). This will limit how long a process
will be tied up with a request.
turn MinSpareServers, MaxSpareServers, and StartServers down
(eg 2,4,4). This will limit the number of httpd processes.
turn MaxClients down (eg 12 or even less)
3. convince slashd to update less often (in the variables table)
4. use Apache::SizeLimit? (I haven't)
The main issue is the way mod_perl works: it means perl is compiled into
each httpd process, and as they run the slash code they cache it all,
compiled, so they get very large. On our machine (redhat 7.0) when memory
got low it started killing random processes to stay alive, and that caused
lots of confusion. Slashd is a pig too. But we finally got it mostly
stable on 128 megs, and now with 192 it is even more mostly stable :)
Another thing is that yesterday we discovered two startup scripts for
slashd - 'slash' and 'slashd'. I think the name changed during in one of
the alpha releases. Anyway removing one of them helped, though we still
get zombied slashds every day. I have mostly assumed it's a problem on
our end since nobody else has been asking about it. But maybe it's not?
-n
--
Nathan Vonnahme na...@th...
senior web developer third sector technologies
http://enteuxis.org/nathan http://thethirdsector.com
On Tue, 5 Jun 2001, Alphabet wrote:
> Hello,
> I have successfully installed Slash 2.0 on my linux box running redhat 7.0.
> I am using mysql 3.23.38 as a database server.
>
> My problem is when I start-up slash, it runs great for the first few minutes,
> then it starts bogging down the linux box to the point that even typing ps -ef
> gives a segfault, and restarting the box takes an hour... :/
>
> I have killed any non-essential processes and that seems to only delay the slow
> down by a minute.
>
> I'm sure if I had more ram I wouldn't experience such a slow down. I am running
> with 128MB. The documentation suggested with tuning I could run Slash faster,
> but I cannot find any documentation on it. Suggestions?
>
> Thanks!
>
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-general
>
|