On Fri, Jan 25, 2013 at 1:22 AM, Kalle Sommer Nielsen <ka...@php.net> wrote:
> Hi > > 2013/1/24 David Soria Parra <d...@php.net>: > > This includes a feature freeze. No new features should be comitted to > > the repository once we tagged the first beta on Feb 7. All outstanding > > features will have to wait for 5.6.0 in a year unless there is a > > This reminds me of yet another old topic: > http://www.serverphorums.com/read.php?7,374842 > > and the one before: > http://markmail.org/message/4w6lcbunw3qfof3c > > > TL;DR, I think it is time to include APC in the core as we so many > times have talked about and most people have agreed, dating back to > the 6.0 meeting in '05 even. > >From what I understood from Rasmus the biggest challenge with merging APC into core is the fact that the compiler currently isn't built to support opcode caching. One of the challenges he pointed out was some of the MAKE_NOP trickery that can make APC's work a bit more complex than necessary. It's possible to optimize the compiler enough to the point that APC's code could be reduced down to very simple opcode caching, putting less stress on the engine and making it easier to maintain. So far from what I've seen by looking at APC's code is that this problem isn't trivial to solve without improving the compiler and makes APC's code a bit bloated. It's also not easy to debug APC either. Judging by the bug reports on bugs web, many of these bugs are also not trivial to reproduce let alone debug and fix. I think that APC should eventually be reduced down to a simple opcode cache and merged into core, but I also think that Rasmus is right about improving the compiler to make opcode caching simpler so that APC doesn't have to do all these tricks. > > -- > regards, > > Kalle Sommer Nielsen > ka...@php.net > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
