Re: optiizer extension import?
| From: | Manuel Lemos | Date: | Wed, 30 Oct 2002 23:56:24 +0000 |
| Subject: | Re: optiizer extension import? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-10359@lists.php.net to get a copy of this message | ||
Hello,
On 10/30/2002 08:10 PM, George Schlossnagle wrote:
I'd like to import an 'optimizer' zend_extension that does peephole optimizations on code. It will be PHP Group licensed. Votes?All right! +1 of course. Anyway, this is the kind of extension that may not be useful when used alone without caching the results to disk or shared memory. The reason is that when you optimize a chunk of code, you may end up not running enough of it to compensate for the time that you took optimizing the code. This is particularly true when you use generic classes that are meant for several purposes but you end up not using it in the same script for all it can do. This was the conclusion that I reached when I started using Zend Optimizer with high levels of optimization that take longer to run. Instead of speeding up code, it was retarding it and causing an huge load on the server. It turned out that using a cache like APC was much better than using Zend Optimizer alone because caching the compiler results got over most of the compilation time overhead. Since APC could not run with Zend Optimizer, I gave up Zend Optimizer. This turns out to become a good selling point for Zend Cache because the difference between using Zend Optimizer and then using Zend Cache even without Zend Optimizer is even more noticeable then using nothing at all and then any cache (Zend Cache, APC, whatever). Zend Optimizer is free but it is like a "greek gift": it is good but often is worse unless you use Zend Cache too. Anyway, I think your optimizer will always be a good thing with either APC or bcompiler. Great job! -- Regards, Manuel Lemos