Hi internals, I've created the RFC https://wiki.php.net/rfc/opcache.no_cache to make the opcode optimizer and JIT available without opcode caching, through a new setting `opcache.no_cache=1`.
So far, the feedback I've gotten is that having the ability to optimize without caching would be useful, but that moving the optimizer into Zend is possibly a better solution. (https://github.com/php/php-src/pull/5504 , announced two weeks ago in https://externals.io/message/109959 "opcache.no_cache prototype: Opcode optimization without caching") To summarize my reasons for creating the RFC without moving the optimizer: - Even with the optimizer moved into PHP's core, I still think there'd be the same use case for a system ini configuration setting to disable caching. (in designs I can imagine) - I consider this useful functionality to have, so I'd rather have a good solution than an ideal solution that currently isn't being worked on (to my knowledge) - I'd prefer creating an RFC with small changes here. - The discussions would be useful for future RFCs in this area. If a viable RFC&implementation to move opcache into core is created (and would conflict with this), I'll postpone this RFC. Thanks, - Tyson -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
