On Tue, Jan 26, 2010 at 11:39 AM, PF4Pylons <[email protected]> wrote: > Hi all > > I was told by a programmer (I am not one :D ) that an application that > runs Pylons via CGI is not going to be performant in a shared hosting > environment and I may not be allowed to use it. As reason for poor > performance the programmer indicated the fact the the server will have > to spawn a new process each time a request comes. > > Is that so?
That's why people don't use CGI in production. But FastCGI was designed specifically to overcome this. Pylons has several deployment options: ProxyPass, mod_wsgi, FastCGI, etc. These are all similar in performance (maybe not identical, but certainly better than CGI). I would start with ProxyPass because it's the most straightforward (just connect Apache to your existing PasteHTTPServer), but it's worth exploring all of them and seeing which one best meets your needs. I haven't used FastCGI so I can't answer your specific questions on it. -- Mike Orr <[email protected]> -- 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.
