2010/2/22 Graham Dumpleton <[email protected]>: > If running 4 processes, seems a but odd that only 1 process is 200 MB. > I presume this is the worst of the processes.
No, no. There are 4 processes in ps/top, each 200 mb. In first mail I mean that 200 mb is average memory used / 1 process. > Presumably the 200MB process has come about due to a large transient > memory requirement for a specific request. Having specific URLs that > generate a large transient memory usage is obviously not good as the > process then keeps that memory. You have 2GB memory so overall not an > issue, but still always better to try and keep memory usage to a > minimum as would at least allow you to have more process in daemon > process group and drop down number of threads in processes to try and > counter any adverse effects from Python GIL when used on multi > processor machine. So I should drop number of threads and increase number of processes? > Do you know whether/what URLs have a large transient memory > requirement? Have you done any profiling on requests so you know which > are the URLs which take memory and or cause a greater CPU load. Not yet, but we have added yesterday backend reponse time to nginx logs, so today we should have clear situation. How about MPM configuration? To be honest I've left it default. Should I tune something there? Best regards, Szymon -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
