PHP 5.5 to include ZO+

Shamil

Well-known member
About a month ago, Zend Optimizer+ was opensourced.

A few days ago, PHP decided to bundle in ZO+ into PHP 5.5.

From performance tests I've read, it looks like ZO+ provides performance improvements over APC. That said, ZO+ does not have wide implementation, due to its former closed nature.

What are your thoughts on this?
 
all in due time, if Zend Optimizer Plus turns out better folks will gravitate towards it eventually :)

benchmarks of Zend Optimizer Plus vs APC look good http://ckon.wordpress.com/2013/02/10/apc-vs-zend-optimizer-plus/

https://wiki.php.net/rfc/optimizerplus

Advantages of Optimizer+ over APC

  1. Performance. Zend Optimizer+ has a consistent performance edge over APC, which, depending on the code, can range between 5 and 20% in terms of requests/second. See Benchmarks section below.
  2. Availability for new PHP versions. Optimizer+ is typically fully compatible with PHP releases even before they come out; While this advantage was rarely realized because of the closed-source nature of the component, once open-source, both Zend and the community will help ensure that it’s always fully compatible with every element of the PHP language, avoiding any lags.
  3. Reliability. Optimizer+ has optional corruption detection capabilities that can prevent a server-wide crash in case of data corruption (e.g. from a faulty implementation of a PHP function in C). This handles one of the very few downsides of using a shared-memory-based-opcode-cache - introducing a shared resource that - if corrupted - could bring down an entire server.
  4. Better compatibility. We strived to make Optimizer+ work with any and all constructs supported by PHP, in exactly the same way they’d behave without it.
Advantages of APC over Optimizer+

  1. Has a data caching API. APC has a data caching API which Optimizer+ does not have.
  2. APC can reclaim memory of old invalidated scripts. APC uses a memory manager and can reclaim memory associated with a script that is no longer in use; Optimizer+ works differently, and marks such memory as ‘dirty’, but never actually reclaims it. Once the dirty percentage climbs above a configurable threshold - Optimizer+ restarts itself. Note that this behavior has both stability advantages and disadvantages.

lack of data caching API in ZO+ might keep some folks sticking with APC
 
Looks interesting. I imagine people will prefer APC due to it being openly available for longer. However i'm gonna give ZO+ a go for sure.
 
have peoples tried it out? APC seems to be a pain these days with segfaults all the time.

with ZO+ being in PECL now I thought I might give it a try
 
php 5.5 beta 1 was released a few days ago

http://php.net/archive/2013.php#id2013-03-21-1

We expect beta 2 around April 4th, but that could get pushed back some (as beta 1 was also pushed back). While dates are something the Php Development Team likes to strive for.... The general idea is to have it stable and secure as possible (as always). So overall its ready when its ready. ;)
 
php 5.5 beta 1 was released a few days ago

http://php.net/archive/2013.php#id2013-03-21-1

We expect beta 2 around April 4th, but that could get pushed back some (as beta 1 was also pushed back). While dates are something the Php Development Team likes to strive for.... The general idea is to have it stable and secure as possible (as always). So overall its ready when its ready. ;)


X1.2 + P5.5 + M5.6 = ???
 
I switched from APC to ZO about a week ago... seems to work fine. {shrug}

I didn't use the data store API in APC, so was no loss really there...
 
Top Bottom