On Tuesday, September 28, 2010 05:36:19 Lionel Young wrote: > I went off on a tangent with this post: > http://groups.google.com/group/turbogears/browse_thread/thread/4dc251a28f0c > e7df > > My goal was to preserve memory with my Turbogears v2 projects, because > I am the only one who uses them. > > When I'm not using the Turbogears projects, I'd like the "paster" > instance killed, and for it to automatically restart when I attempt to > access the URL. > > What technology would allow me to do this? Someone had pointed me to > mod_passenger, which is why I have the link to the post above.
Do you *have* memory issues, or do you just anticipate them? If the former, I suggest you don't do anything unless you really have them. And if the latter... I'm still unsure what mod passenger can do there for you. To me, it looks as if it's ruby only. And IMHO it's a bad idea to try & kill paster instances. There is quite a bit of offset cost starting a TG2 process (configurations being loaded, ORM-mappings declared and set up and so forth). Just killing these & trying to re-start a process on demand will cause hi latency for your users. Instead, use e.g. nginx as low profile HTTP proxy & have a limited number of running paster instances behind him. Diez -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
