Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74384 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3279 invoked from network); 20 May 2014 18:34:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 May 2014 18:34:55 -0000 X-Host-Fingerprint: 217.114.215.11 experimentalworks.net Date: Tue, 20 May 2014 14:34:55 -0400 Received: from [217.114.215.11] ([217.114.215.11:9062] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5E/C0-31952-E40AB735 for ; Tue, 20 May 2014 14:34:55 -0400 To: internals@lists.php.net References: <4ED7146272E04A47B986ED49E771E347BBDA6AAA06@Ikarus.ameusgmbh.intern> User-Agent: slrn/pre1.0.0-18 (Linux) Message-ID: X-Posted-By: 217.114.215.11 Subject: Re: [PHP-DEV] [VOTE] [RFC] 64 bit platform improvements for string length and integer From: dsp@php.net (David Soria Parra) Dmitry Stogov schrieb: > --bcaec548a66d12428804f9c0c7f7 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: quoted-printable > > We had a long discussion with Pierre on IRC and probably come to some > agreement. > However, we always talk as a blind with a deaf, so I can't be completely > sure :) > > We agreed to make 64-bit IS_LONG and 64-bit string length on all 64-bit > systems, but don't change other core data structures (as Nikita suggested). > > The main idea of the changes on top of phpng may be seen at > https://gist.github.com/dstogov/07fcbb60b1b585bcd290 > > I checked the patch on 64-bit Linux. The memory consumption grows, but no > so dramatic. On wordpress home page without opcache the peak_memory_usage() > showed 11043920 bytes insead of 10959456, that mean ~0.8% that we probably > can afford. Note that the original patch on the same test showed ~8% memory > consumption increase on master. > Sounds very good and 0.8% overhead is fine. Can we work on getting this integrated into a v2 of the RFC, continue hopefully constructive discussions for a week or two and then vote again. We aren't in a rush at the moment as php.next is far away.