> On 4 May 2009, at 09:19, Octavian Rasnita wrote: >> >> I have started using fastcgi with a Catalyst app, using it as an external >> server, but I've seen that it works very slow and many requests give a >> timeout error and display a 500 error because of this.
This is a fairly standard sort of problem, so have a debugging aid: http://dev.catalystframework.org/wiki/gettingstarted/howtos/quick_and_dirty_FastCGI The idea here is that this produces a 'known good' minimal FastCGI implementation. Unfortunately, I can't test this properly at the moment due to issues with my development server, but please: - try it - ask me if you have problems, but if you have fixes, change the page! - simplify the page and script if at all possible. *Don't* make it more like a production environment - it's not supposed to be a production environment. *Do* remove any possible complexity (I would prefer a config file to a perl script if at all possible, but lighttpd seems to want absolute paths.) The idea is to remove one variable from an otherwise difficult question. 'My FastCGI setup with server a, configuration b and my custom application' becomes 'my custom application, running in this standard fastcgi configuration'... Cheers, -- Ian. _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/