Hi, Massimo. I didn't cache much at first, and to make sure that caching isn't the source of the problem, I tried removing all caching. No noticeable improvement there. Right now, I'm focused on moving a lot of the model db and global var/settings stuff to modules (but I find this a bit perplexing, as it seems to undermine the whole notion of the MVC framework).
On Monday, June 3, 2013 11:55:02 AM UTC-5, Massimo Di Pierro wrote: > > Mind that caching too much stuff will do that to you. > > On Monday, 3 June 2013 10:04:25 UTC-5, Lamps902 wrote: >> >> Thanks, Roberto. It was eventually growing to something in excess of 80M >> per uwsgi instance, then crashing when all are full. Will try the settings >> you suggested. >> >> On Monday, June 3, 2013 9:32:10 AM UTC-5, Roberto De Ioris wrote: >>> >>> >>> 30-40 MB per worker is pretty normal. >>> >>> To gain memory you can move to multithreading: >>> >>> master = true >>> processes = 2 >>> threads = 2 >>> thread-stacksize = 512 >>> >>> should be good enough >>> >>> Monitoring memory is a good thing, use --reload-on-rss 80 to avoid your >>> app growing up >>> >>> -- >>> Roberto De Ioris >>> http://unbit.it >>> >> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
