A very valuable discussion is going on.... I wish to watch it before taking a ecision on deployment
On Jun 30, 8:11 am, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Jun 30, 7:49 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote: > > > > > > > Sanjay schrieb: > > > > 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. > > > > But frameworks like RoR create new instances for each request and > > > hence is not preferable for high traffic sites. > > > > 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? > > > No. There are many things to say about this, and some have been said. > > But take for example sessions in PHP: they do have to be loaded from > > disk, for every request. Granted, the OS-FS-cache *can* maybe speed that > > up - but serving them from memory all the time is for sure more perfomant. > > > So it is wrong that PHP doesn't have to create any instances - it sure > > does, and even worse, it *can't* possibly use memory-caching techniques > > to prevent that. > > Just because Python is used doesn't mean that sessions are going to be > served from memory all the time. If you are using a multiprocess > configuration for hosting your Python web application, you have to use > a backend data store of some sort which is visible to all processes. > > A robust Python web application and especially one to be hosted in a > multiprocess configuration, cant blindly using memory caching > techniques either. Where it cant use them is where a change through > one process would invalidate cached data in another process. > > There is some discussion about such portability issues in: > > http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading > > Graham- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
