Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65399 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82559 invoked from network); 29 Jan 2013 14:33:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jan 2013 14:33:08 -0000 Authentication-Results: pb1.pair.com header.from=lars@strojny.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lars@strojny.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain strojny.net from 46.4.40.248 cause and error) X-PHP-List-Original-Sender: lars@strojny.net X-Host-Fingerprint: 46.4.40.248 milch.schokokeks.org Received: from [46.4.40.248] ([46.4.40.248:48373] helo=milch.schokokeks.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3A/7F-10721-2ADD7015 for ; Tue, 29 Jan 2013 09:33:07 -0500 Received: from [192.168.1.91] (p5099f5c8.dip0.t-ipconnect.de [::ffff:80.153.245.200]) (AUTH: PLAIN lars@schokokeks.org, TLS: TLSv1/SSLv3,128bits,AES128-SHA) by milch.schokokeks.org with ESMTPSA; Tue, 29 Jan 2013 15:33:02 +0100 id 0000000000000026.000000005107DD9E.000008D0 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) In-Reply-To: <5107DB01.6050900@lerdorf.com> Date: Tue, 29 Jan 2013 15:33:01 +0100 Cc: Nikita Popov , "internals@lists.php.net" Content-Transfer-Encoding: quoted-printable Message-ID: <9F2D34C6-F9FE-4F36-9632-DD52D9F7893F@strojny.net> References: <5d21b42656d49b4a71d9f808541bd745@mail.gmail.com> <252ADB1A-2660-4A45-B859-B92DA2C8B8D8@gmail.com> <5107CEEB.9080003@zerocue.com> <5107D429.60001@lerdorf.com> <5107DB01.6050900@lerdorf.com> To: Rasmus Lerdorf X-Mailer: Apple Mail (2.1499) Subject: Re: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP distribution From: lars@strojny.net (Lars Strojny) Hi Zeev, Am 29.01.2013 um 15:21 schrieb Rasmus Lerdorf : > On 01/29/2013 06:13 AM, Nikita Popov wrote: >=20 >> I'm not sure I fully understand this. The RFC claims that Optimizer+ = is >> already *now* fully compatible with PHP 5.5. And that it was also >> compatible when PHP 5.4 was released. So they lack of a working and = free >> opcode cache clearly wasn't the issue. My guess is rather that the = lack >> of APC support (as in specifically APC and not just some opcode = cache) >> was an issue. Either because people didn't know about alternatives = (APC >> after all is the go-to opcode cache), didn't want to try them or had >> software tightly integrated with APC (and in particular its user = cache). [...] I personally find it quite cool, that Zend considers open sourcing its = Optimizer+ product. I=92m obviously just guessing, but I am halfway = sure, that APC (and XCache etc.) have a lot to do with Zend being = willing to do that move. In a sense that it helped making opcode caches = a commodity. Maybe that=92s a small solace for the countless hours that = where spent on APC. To get more practical, I see the following steps = going forward: 1.) Zend releases a first open sourced version of Optimizer+ on PECL = (or somewhere else) 2.) We as a community can have a look at the code 3.) We vote on the RFC 3a.) Question a) Should Optimizer+ be included in core: yes/no 3b.) Question b) If yes, may the inclusion delay 5.5 by X month: yes/no 4.) The proposers make sure it works with ZTS as well (this obviously = doesn=92t exclude help from outside contributors) @Zeev, out of interest, how much time does Zend plan to spend on = maintaining Optimizer+ in the core for the foreseeable future? cu, Lars=