On Fri, Aug 6, 2010 at 2:00 AM, Graham Dumpleton <[email protected]> wrote: > Are the operations of the Python web application I/O bounds, ie., > database accesses etc, or compute bound, ie., lot of algorithmic > calculations being done?
most pages are simple and fast, ~20 requests/sec although slowly growing with increased usage. there is a django/piston rest api that's getting more and more usage. nothing special but there are a lot of static files going through apache. > What is the Python web application, ie., is it using a far Python web > framework and use a lot of memory and have to load a lot of code on > start? django, average memory usage for django project. not a lot of memory. memory is not a problem, ec2 instance with all services uses < 30%. any recommendations that would use more memory but result in better/faster handling of requests is acceptable. >> maximum-requests=100 > > This option should never be set in a production environment, you > always want to ensure process stays persistent and is not restarted. > > Why are you setting this? If your Python web application keeps growing > in memory use over time, you need to work out why. it was 10000, i've probably changed it by accident when i pasted it. i've found this setting in: http://github.com/lincolnloop/django-best-practices/blob/master/examples/apache.conf i'll remove it. > Sorry for delayed reply. Mail reader had marked message as read and > didn't see you had replied since. not a problem, thanks a lot for taking the time to comment on this. Aljosa -- 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.
