On May 7, 11:50 am, "Vlad K." <[email protected]> wrote: > On 05/07/2012 05:37 PM, Jonathan Vanasco wrote: > > > - eventually i would refactor the code to use a SOA setup and have a > > dedicated daemon handle the large stuff. > > But doesn't that suffer from the same set of problems? If the (daemon) > process persists in memory, it doesn't matter if it's the wsgi app or a > SOA approach. Unless you put it on a different server, but it then > saturates memory there instead of the wsgi app server.
Yes. but if you're at the size where it needs to be a SOA , you pretty much need to have that daemon running nonstop. So you have a single process that is 'eternally' allocated 256MB (or whatever) and does all the grunt work - and you never run into an issue with multiple app servers spiking up the memory usage. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
