Re: Server load issues

Hi Robby!

I´m no fcgi expert nor am I a computer expert at all, so maybe this is 
just this type of really silly replies. ;)
If so, just forget it.

 From what I see I wouldnt think this is a fcgi configuration problem. I 
think the problem lies within your app.

A cgi-Script using 100 and another process nearly using 200 MB doenst 
look healthy to me. What should fcgi do better than this?
I got 10 MB processes and I think they are already to big!

You told, that the processes slowly go up on swap/ram over time.

Aren´t these absolutely clear signs for a memory leackage?

I see some small dispatch.fcgis. They didnt take much time as top tells. 
They just answered few requests and therefore the memory leackage isnt a 
big prob.
But the dispatch.fcgis runnung for some time take a lot of mem. They 
answered a lot request an with every request you loose memory which isnt 
freed after the request.

If so:
solution 1)
Optimize dispatch.cgi
Use strict
Free memory after each request at the end of the loop
Hope that the perl garbage collector works correctly

solution 2)
Use a counter in the request loop
exit the script every 100 or 1000 or whatever requests
So fcgi will just restart the process


The best would of course be a combination of both, I think.

greetings
Albert
___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/