On Thu, Feb 14, 2013 at 7:21 PM, Zeev Suraski <z...@zend.com> wrote: > O+ does perform some optimizations in addition to caching code, in a pretty > sophisticated manner actually (block optimizations). Optimizations - which > can be expensive to carry out - are definitely a good fit with an opcode > cache, that ensures that you wouldn't have to do these optimizations more > than once. I'm obviously subjective but I think the name Optimizer+ does a > good job at suggesting that it's both an Optimizer but also something else. > Perhaps we should call it OptiCache? :) > >> Questions (I haven't dug through the code): >> >> - What do CLI processes share? > > IIRC nothing, presently it's not very useful for CLI except for testing > (it'll only apply to a single run). I could be wrong though, Dmitry?
Well, if it does block-level optimizations, that is already enough to make it useful for CLI-scripts, as even though caching is not relevant for long-running processes, optimizations should make things faster. Are optimizations documented? -- Alexey Zakhlestin, http://github.com/indeyets -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
