Steve Underwood writes:
> Brian Grossman wrote:
>
> > > Has anyone experimented with trying to turn sqwebmail into an Apache
> > > module? Webmail looks like its here to stay, and making is run at the
> >
> > Try using it as a fastcgi program. Nearly the same speed benefit (skip
> > exec, skip DB connect), but more flexible, and less likely to crash apache.
>
> That was the other option I was considering - either fastcgi, or one of the
> other forms of persistent CGI which exist now. I haven't looked at these
> enough to judge their various merits, but at least one of them must be able to
> do the job. I realise the current code wasn't written with persistence in mind
> (there is no reason wht it should have been), so the task may not be totally
> trival. It seems like there should be some really significant performance
> benefits from getting rid of those exec's, though.
>
> Maybe my next step should be to study the relative merits of the various
> persistent CGI mechanisms.
I doubt that persistent CGI makes much of a difference. The overhead of an
exec is too small to make much of a difference. Unless you're really
running a huge server, you are not accomplishing anything useful.
It used to be that the prevalent reason for persistent CGIs would really be
persistent connections to the database back-end that's used for
authentication. This is no longer a factor, with the authdaemon module
which nicely encapsulates authentication into a persistent background
daemon process.
--
Sam
