Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65174 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77783 invoked from network); 25 Jan 2013 16:53:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jan 2013 16:53:37 -0000 Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.54 as permitted sender) X-PHP-List-Original-Sender: julienpauli@gmail.com X-Host-Fingerprint: 209.85.212.54 mail-vb0-f54.google.com Received: from [209.85.212.54] ([209.85.212.54:61207] helo=mail-vb0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A9/A8-03402-198B2015 for ; Fri, 25 Jan 2013 11:53:37 -0500 Received: by mail-vb0-f54.google.com with SMTP id l1so427914vba.27 for ; Fri, 25 Jan 2013 08:53:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=1BZWnzX+eo4G/BwISf3zs3wo4VTcrlHx+W3rj+eBdIY=; b=oyV+NXj57/5W2wTjo+41MrzZX7qcwzxBUchP/uyjpnMDo1P0oZiMRxNjO+caugEB8g M5WIs0/CXV31ObGvM3Vj5GOVaaenpEAh94oO+89t7ZFbyguaZFziWSPCEKaxiyySsM/4 EezbBx5pEv9HzDSoDx218pMYpkgP7Gfy0V0n6L4uEFY6sxu+aufTR07wKC9C9pXx743+ j3E9vSgzHAHgYbSck3+loT6ppAXhd8H1KeGnu24qzs5BoKHp8T6anJGFWqn7omF9abGE veQQ07WVP4qEm8NrfddjK5fm2mfh7ZNFL90dq49lNDgyWp++YiXrJ1gun9uz+Gh99TAX Qg1Q== X-Received: by 10.52.28.176 with SMTP id c16mr5718500vdh.126.1359132814138; Fri, 25 Jan 2013 08:53:34 -0800 (PST) MIME-Version: 1.0 Sender: julienpauli@gmail.com Received: by 10.220.140.132 with HTTP; Fri, 25 Jan 2013 08:52:54 -0800 (PST) In-Reply-To: <6AA61A4F-ABF0-4FF2-A509-3FE70297B744@php.net> References: <51023AB1.2010607@b1-systems.de> <51024016.4010005@lerdorf.com> <6AA61A4F-ABF0-4FF2-A509-3FE70297B744@php.net> Date: Fri, 25 Jan 2013 17:52:54 +0100 X-Google-Sender-Auth: jwHCTAjicguHijyW_MyspAgcKYM Message-ID: To: Will Fitch Cc: Zeev Suraski , Rasmus Lerdorf , Ralf Lang , internals@lists.php.net Content-Type: multipart/alternative; boundary=20cf3079bdba96dcd004d41fc405 Subject: Re: [PHP-DEV] HEADS UP: Upcoming Feature Freeze for PHP 5.5.0 From: jpauli@php.net (Julien Pauli) --20cf3079bdba96dcd004d41fc405 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jan 25, 2013 at 5:47 PM, Will Fitch wrote: > > On Jan 25, 2013, at 11:25 AM, Zeev Suraski wrote: > > >> Either by a number of people stepping up to help with the existing APC > > code, or > >> perhaps more realistically making it a priority in PHP 5.6 to streamline > > the > >> engine and the executor for opcode caching and either including a > > heavily > >> simplified version of APC or writing a new one. > >> > >> One thing I can guarantee is that if we add it to core in its current > > condition it > >> will delay 5.5 by 6+ months if not longer. > > > > There's another option. We have the Optimizer+ component which is > > current, a bit faster than APC, worked with PHP 5.4 from the get go and > > already fully supports 5.5 - and now that it's been free for use for > > several years, we'd actually be happy to opensource it and make it a part > > of core. An extra benefit would be that we'd commit to maintain it, > > although of course, community contribution will be very welcome. > > Here too, it's code with a very long history, some of which even predates > > PHP 4.0. But It Works(tm), and we could put some effort into cleaning it > > up and beautifying it. > > I like the idea. If this was implemented in core, and the need for APC > opcode caching disappeared, would APC still be actively maintained for > userland functions (e.g. apc_store, apc_*)? > Well, the APC idea was anyway to merge an Opcode cache to Core, and only an Opcode cache (correct if I'm wrong). apc_store() etc... are userland shared memory function, and should be migrated into another extensions, on which we could then allocate devs to work on, new ideas, etc... Julien.Pauli --20cf3079bdba96dcd004d41fc405--