<HTML>
<HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
Michael,
<br />
<br />I have a question that is semi-related. Openwebmail recommends using SpeedyCGI with it (not to be confused with FastCGI). I do not believe that the pkg from Solarspeed comes with this enabled but I am curious as to your opinion on it. SpeedyCGI appears to keeps the perl module in memory (persistent) to speed repetitive execution. This would of course mean higher memory usage. From my limited understanding, this can be applied to just a single set of perl scripts, such as the Openwebmail application, rather than site wide.
<br />
<br />Are there drawbacks to using SpeedyCGI and was it a specific choice you made to not include it when creating the Solarspeed Openwebmail package? I suspect that with my limited knowledge in this area, it is best to ask the opinion of you and others before proceeding to use it.
<br />
<br />Dan Porter
<br />Twin Wolf Technology Group
<br /><font size="2">
<br />
<br /><b>---------- Original Message
-----------</b>
<br />
From: Michael Stauber <mstauber@blueonyx.it>
<br />
To: BlueOnyx General Mailing List <blueonyx@mail.blueonyx.it>
<br />
Sent: Thu, 20 Oct 2011 16:59:56 +0200
<br />
Subject: [BlueOnyx:08873] Re: Neat blog comparing PHP handlers
<br />
<br />> Hi Jeff,
<br />>
<br />>
> Also the revelation that if you are using suPHP - Opcode type caches
<br />>
> (xcache, APC, eAccellerator) will not work and therefore there is no
<br />>
> benefit at all to run then.
<br />>
<br />>
Yeah, that's true.
<br />>
<br />>
> The item goes on to say that FASTCGI can use Opcode caches, however the
<br />>
> trade off is higher memory use.
<br />>
>
<br />>
> Anyway - here's the item:
<br />>
>
<br />>
> <a target="_blank" href="http://boomshadow.net/tech/php-handlers/">http://boomshadow.net/tech/php-handlers/</a>
<br />>
<br />>
This is indeed a very good article. To me it doesn't reveal anything new, but
<br />>
it sums it up nicely on one page, so it is a good reference for explaining
<br />>
things whenever this topic comes up.
<br />>
<br />>
As you can see, all the different methods (DSO, CGI, suPHP, FastCGI) each have
<br />>
some benefits and some drawbacks. Unfortunately there is no "one size fits
<br />>
all" solution that has all the benefits.
<br />>
<br />>
On Blueonyx we have the choices between running sites with PHP through DSO or
<br />>
suPHP.
<br />>
<br />>
The lower memory usage and better security model make suPHP a much desired and
<br />>
welcome solution in a shared hosting environment. The drawback of course is
<br />>
higher CPU usage, slightly slower performance (than DSO) and (as you noticed)
<br />>
optional accelerators and caches won't really work.
<br />>
<br />>
For sites that require speedy execution, have a high CPU demand and would
<br />>
greatly benefit from accelerators, DSO is - at this time - the only
<br />>
alternative on BlueOnyx. Which of course is bought at the costs of lower
<br />>
security and the old UID/GID problems that such a site will have problems
<br />>
having the scripts upload or write files unless you carefully micro-manage the
<br />>
permissions and ownerships.
<br />>
<br />>
I'm not really comfortable of adding FastCGI to the mix of available options.
<br />>
FastCGI isn't "mainline" as far as CentOS is concerned. It's only
served out
<br />>
of the "extras" YUM repository, which also contains a whole bag of
troubles
<br />>
for us if enabled. Although it sure would incorporate some of the benefits of
<br />>
DSO with those of suPHP. At the cost of a higher memory usage and a much more
<br />>
complex GUI to manage it all. And the risk of things breaking during one YUM
<br />>
update or other, because the dependencies get all tangled up.
<br />>
<br />>
So yeah, as is one needs to carefully examine his needs and as of wether DSO
<br />>
or suPHP are the best choices for the site(s) in question.
<br />>
<br />>
--
<br />>
With best regards
<br />>
<br />>
Michael Stauber
<br />>
_______________________________________________
<br />>
Blueonyx mailing list
<br />>
Blueonyx@mail.blueonyx.it
<br />>
<a target="_blank" href="http://mail.blueonyx.it/mailman/listinfo/blueonyx">http://mail.blueonyx.it/mailman/listinfo/blueonyx</a>
<br /><b>------- End of Original Message
-------</b>
<br />
</font>
</BODY>
</HTML>