[jifty-devel] Production hosting setup/config

Jesse Vincent jesse at bestpractical.com
Tue Feb 9 11:51:37 EST 2010

On Mon, Feb 08, 2010 at 04:21:08PM +1100, Mark Aufflick wrote:
> Jesse, I saw your email (from 2007) about SpamAssassin's apache style perl
> pre-forking. Did you ever go down that road? I'm thinking a fast,
> multi-child, daemon proxied through apache is the simplest fast way to go.
> I'm going to see if Net::Server::PreFork is good enough, but I've seen
> inconsistent reports about it's performance.
> http://www.mail-archive.com/jifty-devel@lists.jifty.org/msg00905.html
> <http://www.mail-archive.com/jifty-devel@lists.jifty.org/msg00905.html>The
> other advantage of going to a standalone process (instead of fastcgi) is
> that the frontend could be Perlbal (or any other proxy) instead of Apache or
> lighty etc.

jifty server with Net::Server::Prefork is something we do for anything
where we're using Jifty's Comet support, but it's not something we've
tested on an internet-scale webservice.

More information about the jifty-devel mailing list