Hi internals,
https://wiki.php.net/rfc/opcache.no_cache has been declined, with 10 yes votes and 13 no votes.
The "If you voted no, why?" section indicates that there was broad support for moving opcache optimizations outside of the zend_extension and into core instead of this approach.
After the RFC ended, I added a section with some rough ideas for implementation details of how moving optimizations into core instead would be done (while continuing to support existing php use cases efficiently)
in https://wiki.php.net/rfc/opcache.no_cache#ideas_on_moving_the_optimizer_into_core_instead ,
but ran into roadblocks trying to implement it.
I probably won't end up implementing this, because it's a much more extensive refactoring.
I'm not familiar enough with opcache to know if what I'd implement would end up working on all platforms (threaded vs non-threaded, windows memory management, etc),
or if it'd interfere with existing debuggers/profiles, or have other shortcomings I didn't anticipate.
Thanks,
- Tyson
On Sat, Jun 13, 2020 at 5:08 PM tyson andre tysonandre775@hotmail.com
wrote:
Hi internals,
https://wiki.php.net/rfc/opcache.no_cache has been declined, with 10 yes
votes and 13 no votes.The "If you voted no, why?" section indicates that there was broad support
for moving opcache optimizations outside of the zend_extension and into
core instead of this approach.After the RFC ended, I added a section with some rough ideas for
implementation details of how moving optimizations into core instead would
be done (while continuing to support existing php use cases efficiently)
in
https://wiki.php.net/rfc/opcache.no_cache#ideas_on_moving_the_optimizer_into_core_instead
,
but ran into roadblocks trying to implement it.
To be clear, "move into core" means moving optimizations into Zend/ and
making them part of the compilation process (optionally). They shouldn't be
in a separate ext/optimizer extension -- that would be not much better than
having them in ext/opcache :)
Nikita
I probably won't end up implementing this, because it's a much more
extensive refactoring.
I'm not familiar enough with opcache to know if what I'd implement would
end up working on all platforms (threaded vs non-threaded, windows memory
management, etc),
or if it'd interfere with existing debuggers/profiles, or have other
shortcomings I didn't anticipate.Thanks,
- Tyson