Sanjay wrote: > Hi All, > > It might be a novice question on deployment. I am a TurboGears guy > since long, but still new to certain things like deployment etc. So, > pl. bear with me if my words are not exact and technical. > > A couple of days back I was presenting about TurboGears to a PHP web > architect. He was of the view that PHP behind Apache is faster because > it doesn't have to create new instances per request or queue requests. > He's got it right except for that it is the opposite way around :)
TG is (usually) a multi-threaded long running application for the good (modules are cached in memory when imported, import-time initialization stuff is done only once in the lifetime of a process...) and the bad (you have to be careful with shared memory among threads, leaking memory...) Ian wrote some time ago a good post that mentions this: http://blog.ianbicking.org/2008/01/12/what-php-deployment-gets-right/ > But frameworks like RoR create new instances for each request and > hence is not preferable for high traffic sites. > AFAIK Rails' model of execution is similar to TG's > CherryPy applications, as I have understood, do similar thing as PHP > and should be at par. So, reverse proxing a TG Application behind > Apache or NginX should be at par with a PHP+Apache deployment. > > Is my understanding ok? > Nope :) > What about TG 2.0? > TG2 and Pylons are similar to TG1 in this sense: An instance is a long running app, usually multithreaded, that can serve arbitrary number of requests in its lifetime. Alberto > thanks > Sanjay > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
