Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127733
Precedence: bulk
MIME-Version: 1.0
References: <faff22ce-dcb9-4013-80d9-ceddd0de5a12@mabe.berlin>
 <73D7B135-ABF8-4EFC-BF16-EA26A5BD1B7A@cmpct.info> <B86F771B-1E5C-4D5A-9A22-3F8272A562B7@php.net>
 <CAJmy8YHtUXNPLvmmncSjtgNGT4d+e0DfoZgRziih09zfZ5ABdg@mail.gmail.com> <5747e268-1176-4b87-ba58-2a767d45006b@mabe.berlin>
In-Reply-To: <5747e268-1176-4b87-ba58-2a767d45006b@mabe.berlin>
Date: Fri, 20 Jun 2025 14:21:39 +0200
Message-ID: <CAJmy8YFXndGvtwc1HbSK_SHsauW9gXgThOWEme-feYgQjV+frw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Drop support for 32bit builds
To: Marc Bennewitz <marc@mabe.berlin>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: divinity76@gmail.com (Hans Henrik Bergan)

On Fri, 20 Jun 2025 at 13:20, Marc Bennewitz <marc@mabe.berlin> wrote:
>
>
> On 19.06.25 18:55, Hans Henrik Bergan wrote:
>
> On Thu, Jun 19, 2025, 18:24 Ben Ramsey <ramsey@php.net> wrote:
>>
>> > On Jun 19, 2025, at 11:08, Calvin Buckley <calvin@cmpct.info> wrote:
>> >
>> > On Jun 19, 2025, at 11:08=E2=80=AFAM, Marc Bennewitz <marc@mabe.berlin=
> wrote:
>> >>
>> >> Hi,
>> >>
>> >> During the discussion about the year 2038 issue it turned out that ma=
ybe it's time to drop support for 32-bit of PHP completely.
>> >>
>> >> Based on that I have created an RFC to deprecate 32-bit build in 8.ne=
xt and drop support for it in 9.
>> >>
>> >> RFC: https://wiki.php.net/rfc/drop_32bit_support
>> >
>> > I think the biggest arguments against this would be:
>> >
>> > - embedded systems; think of PHP in use for i.e. router web UIs. While=
 I
>> > suspect a lot of these are going to be i.e. AArch64/RV64 in the future=
,
>> > there might be a long tail of existing systems. Of course, how many
>> > would upgrade to PHP 9?
>> >
>> > - WebAssembly; I don't know how widespread the Memory64 proposal is ye=
t.
>> > We're using WebAssembly in the docs pages for runnable examples.
>> >
>> > And some niche cases like i.e. iSH (which emulates x86-32 on iOS).
>> >
>> > The other options include making zend_long always 64-bit and accept th=
e
>> > performance penalty for 32-bit, or making 32-bit best-effort rather th=
an
>> > providing any guarantees.
>>
>>
>> Last night, I was giving some thought to reviving Andrea=E2=80=99s Big I=
nteger RFC[^1]. This is something I=E2=80=99ve wanted for a long time (espe=
cially for my ramsey/uuid library, among other things).
>>
>> Andrea had a work-in-progress PR[^2]. I=E2=80=99m not sure the current s=
tate of it. It=E2=80=99s from 2014 and was originally written for phpng. I =
had planned to start teasing out bits of it into a new branch based on the =
current master branch to see how far I could get with it. I wouldn=E2=80=99=
t mind some help with that, if anyone=E2=80=99s interested. :-)
>>
>> If we are able to finish what Andrea started, then we would not need to =
drop support for 32bit builds.
>>
>> Cheers,
>> Ben
>>
>>
>> [^1]: https://wiki.php.net/rfc/bigint
>> [^2]: https://github.com/php/php-src/pull/876
>
>
>
>
> Smallest ramnode.com VPS has 512MB ram. I would run 32bit PHP on a 512mb =
ram VPS. I'm not longer a ramnode customer, but I used to be.
> I for one would be sad to see 32bit PHP go.
>
> I have done a quick test on current master with Symfony :
>
> Without OPCache
> x32: mem: 16777216b, t: 0.15017914772034s
> x64: mem: 23068672b, t: 0.072926998138428s
>
> With OPCache
> x32: mem: 4194304b, t: 0.01033878326416s
> x64: mem: 4194304b, t: 0.0080580711364746s
>
> As you can see, with opcache enabled it's taking the same amount of memor=
y. (I don't know why ... did mostly the same setup as the configure-x32 GH =
action)
>

the php memory allocator allocate large chunks from the OS, checking
the OS-allocated memory doesn't tell the whole story,
it's possible that the actual usage memory between 32/64 non-OPCache was mi=
nor,
can you try:

register_shutdown_function(function () {
    var_dump([
        "memory_get_usage(real_usage:false)" =3D>
memory_get_usage(real_usage: false),
        "memory_get_usage(real_usage:true)" =3D>
memory_get_usage(real_usage: true),
        "memory_get_peak_usage(real_usage:false)" =3D>
memory_get_peak_usage(real_usage: false),
        "memory_get_peak_usage(real_usage:true)" =3D>
memory_get_peak_usage(real_usage: true),
    ]);
});