Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76300 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47157 invoked from network); 31 Jul 2014 20:21:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Jul 2014 20:21:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.116.216 imap10-3.ox.privateemail.com Received: from [192.64.116.216] ([192.64.116.216:58925] helo=imap10-3.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F7/84-09748-E55AAD35 for ; Thu, 31 Jul 2014 16:21:52 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 203962400DD; Thu, 31 Jul 2014 16:22:07 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap10.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap10.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ORkYFrVu7D1S; Thu, 31 Jul 2014 16:22:06 -0400 (EDT) Received: from [192.168.0.15] (unknown [90.210.122.167]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 13CBD2400DC; Thu, 31 Jul 2014 16:22:05 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: <21.50.09748.8007AD35@pb1.pair.com> Date: Thu, 31 Jul 2014 21:22:02 +0100 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: References: <25.82.08559.C1852D35@pb1.pair.com> <21.50.09748.8007AD35@pb1.pair.com> To: Pascal Chevrel X-Mailer: Apple Mail (2.1878.6) Subject: Re: [PHP-DEV] Reporting bugs for phpng From: ajf@ajf.me (Andrea Faulds) On 31 Jul 2014, at 17:34, Pascal Chevrel wrote: > The problem is that the more arrays I load, the more memory PHPNG = consumes while current versions of PHP have that value mostly stable. I = have with PHPNG a scalability issue I don't have with regular PHP. If = tomorrow I increase the number of languages I support in my app from 70 = to 200 (which is my long term goal btw), I would probably need to set = memory_limit to 700MB which seems honestly crazy when PHP 5.x needs 8MB = for the same script to run at the same speed. As an end user, I think = it's a bug not a feature, I hope you understand my point of view :). This isn=92t so much a response to Pascal, more a question for the rest = of you. My apologies if I=92m misunderstanding this internally. As the = array is in opcache, we can just use it directly without copying, right? = In which case, shouldn=92t Pascal=92s issue not be happening, or is = Pascal not using opcache? Or, are we copying each time we run the = script? In which case, why aren=92t we using opcache=92s copy? -- Andrea Faulds http://ajf.me/