Hi internals,
If there are no unexpected issues,
then voting will start on https://wiki.php.net/rfc/opcache.no_cache in 2 days,
on May 30th.
Thanks,
- Tyson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi tyson,
Thanks for your RFC. As ReactPHP users this is a very welcome change. Right
now we have to enable file_cache only for the optimizations, as there's no
real benefit of the full opcache in long-running CLI apps. Having this
setting would allow us to even stop using file_cache but get the o
Hi internals,
https://wiki.php.net/rfc/opcache.no_cache has been updated.
Instead of opcache.no_cache=1, opcache.enable_cache=0 is now used to disable
caching.
In the RFC, I wrote that opcache_get_status() now includes the following new
booleans
- `optimizations_enabled`, which is true if any
> In my opinion, configuration names should never be "in the negative".
> Instead of defaulting to opcache.no_cache=0, default to opcache.cache=1.
I see your point - there are only a few negative ini names I see in phpinfo()
(disable_functions, disable_cache), and those are for lists of strings
On Sat, 16 May 2020, tyson andre wrote:
> 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`.
In my opinion, configuration names should never be "in the negative".
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 usefu
