What are the advantages? I read many good reviews on XCache or APC + memcached, but I'm not sure if memcached has any advantage for a relatively small boards with 500K posts/2000 visits a day/850MB SQLDrop APC and use Zend Optimizer
Here's a good overview of the relative merits straight from the horse's mouth: https://wiki.php.net/rfc/optimizerplusWhat are the advantages?
Advantages of Optimizer+ over APC
Advantages of APC over Optimizer+
- 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.
- 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.
- 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.
- 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.
- Has a data caching API. APC has a data caching API which Optimizer+ does not have.
- 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.
Here's a good overview of the relative merits straight from the horse's mouth: https://wiki.php.net/rfc/optimizerplus
Notably:
If I would like Zend Optimizer+ to do data caching, would the configuration be on the server level or XF level (config.php? or anything else) or both?Considering that it's an opcode cache only, it doesn't do data caching (unlike APC which does), it would seem that no configuration is actually needed...
ZO+ doesn't offer data caching period.If I would like Zend Optimizer+ to do data caching, would the configuration be on the server level or XF level (config.php? or anything else) or both?
So how does it better/faster than APC? I saw the benchmarks on PHP website that shows 5-20% improvement over APC. Is that with data caching disabled?ZO+ doesn't offer data caching period.
So how does it better/faster than APC? I saw the benchmarks on PHP website that shows 5-20% improvement over APC. Is that with data caching disabled?
So the question is how the benchmark would look like if APC would work with data cache and opcode versus ZO+ with opcode cache alone. Are there any benchmarks like that somewhere?It's an opcode cache, not a data cache. It's opcode cache is better than APCs.
Not that I know of but you can use something like memcached for data cache and ZO+. No reason to sacrifice data cache just for ZO+.So the question is how the benchmark would look like if APC would work with data cache and opcode versus ZO+ with opcode cache alone. Are there any benchmarks like that somewhere?
memcached should be configured on the server level or/and Xenforo level? I saw some lines that are one should add to the config.php file once memcached installed, but other then that, is there anything else?Not that I know of but you can use something like memcached for data cache and ZO+. No reason to sacrifice data cache just for ZO+.
I personally use Redis for data caching in PHP apps but XenForo doesn't support this in the core (yet).
With Zend Optimizer Plus, is their an admin area like in xcache and APC?
We use essential cookies to make this site work, and optional cookies to enhance your experience.