[rt-users] standalone_httpd

[Les Mikesell]

On Mon, 2005-08-08 at 12:50, Rich West wrote:
> >>> Is this efficient enough to use as the standard way of running RT?  It
> >>> might eliminate a lot of installation problems and if you wanted it
> >>> as a virtual host you could easily run on an odd port number and play
> >>> some tricks with Apache's ProxyPass or RewriteRules to hide the fact
> >>> that it isn't the same web server.
> >>>
> >>>> Unless things have changed, standalone is single threaded. That means
> >>>> it can only process one request at a time. If someone runs a long
> >>>> query everyone else will be waiting.
> >>>>
> >>> Unfortunately, this is true.  It is single threaded, and it can be a 
> >>> huge performance hit.
> >>
> 
> Although.. just a thought here.. if it were written so as to be a 
> forking web server (fork off a standalone process to handle the current 
> request then exit upon completion), with a limit on the number of 
> currently running forks (so as to prevent the server from being 
> overloaded too easily), it would probably be comparable in performance 
> without the complexity..

Forking a big process like perl+application on every hit would be
pretty expensive too.  I think what it would really need is to
pre-fork 3 or 4 processes if that can be done without making it
just as complicated as fastgci.

-- 
  Les Mikesell
   les at futuresource.com