Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74214
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.179 as permitted sender)
MIME-Version: 1.0
Date: Thu, 15 May 2014 01:33:09 +0200
Message-ID: <CAEZPtU6xpcGHTTrohn3QTR==2e1Umv4KGsb91JXU0qN-sP2Yjg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: [rfc] 64bit usage, actual memory usage using real life apps
From: pierre.php@gmail.com (Pierre Joye)

hi,

So here are the first numbers:


 peak mem usage:

Wordpress master:  24.33Mb
Wordpress str_size_and_int64: 25.72Mb
delta 5.4%

Symfony master: 26.59Mb
Symfony str_size_and_int64: 27.19Mb
delta 2.2%

Drupal master: 23.46MB
Drupal str_size_and_int64: 24.60Mb
delta 4.63%

There is indeed more memory used but it is less than one could expect
and very acceptable given the benefits provided by the patch.

Also we may see more gains if class/variable/etc names use int32
instead of size_t, as Stas pointed out it makes little sense in this
case and the implementation is much safer than any other areas in the
core (or other extensions).

I feel confident that we can even get better results with phpng, once
we get the time to actually merge the 64bit patch and do further
analyzes while stabilizing phpng.

I have to ask anyone to actually look at these numbers and the
benefits (see the other thread "on memory usage with the 64bit patch,
and interpretation of various numbers").

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org