Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73941
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CA+9eiLu-xD00mQN4QzsRMdnT5t2KU8EKOjejMjx30wYtp50NnQ@mail.gmail.com>
References: <CA+9eiLtKFMWn7AXyS3_fni1Dyerx3DUW7imZ08P9gLr_FY=TaA@mail.gmail.com>
	<CAEZPtU6Eh6pXOXyX_pVEm2bcsZtfoLwLND-HeCuk3xMuwpc4xQ@mail.gmail.com>
	<CA+9eiLvHLWuA81s-oQY4Q7qydFRgskYDUOL6tSctyoe5Aw1z4w@mail.gmail.com>
	<CAEZPtU6VtgtCBb9miiOUAOZVNGfEt5+BkBLsTO57Aiuvk6JFGg@mail.gmail.com>
	<CA+9eiLtojqZZ-5SQSvitNkwL=Knp7NxwKSth3dHYNsFZDcAeRA@mail.gmail.com>
	<CAEZPtU6VrgxCBGbNTpzQTK_TWf4VB4840dBmzraJc8YgORR7Dw@mail.gmail.com>
	<CA+9eiLtT_wzVsv+p=m7vwU72XsAOi6yTndsUak57nd-MDudFZw@mail.gmail.com>
	<CAEZPtU6vvP0zQjrOOWrrcwJAVW7UFEnx4tRzk+ZE4S5vf3d67A@mail.gmail.com>
	<CA+9eiLu-xD00mQN4QzsRMdnT5t2KU8EKOjejMjx30wYtp50NnQ@mail.gmail.com>
Date: Tue, 6 May 2014 08:41:30 +0200
Message-ID: <CAEZPtU4f4sXdJ+RpPS-dXPeqdnHcQV-GzDwSrXzmYW+jm9pAvw@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] phpng: Refactored PHP Engine with Big Performance Improvement
From: pierre.php@gmail.com (Pierre Joye)

On Tue, May 6, 2014 at 8:25 AM, Dmitry Stogov <dmitry@zend.com> wrote:
>
>
>
> On Tue, May 6, 2014 at 10:14 AM, Pierre Joye <pierre.php@gmail.com> wrote:
>>
>> On Tue, May 6, 2014 at 7:56 AM, Dmitry Stogov <dmitry@zend.com> wrote:
>> > int64 proposal is still in draft for very long time.
>>
>> Sorry, but it was proposed and rejected because of the changes were
>> too big for the 5.x serie. It has been said, as arguments for the no,
>> that it would not be a problem for php 6. We are so far.
>
>
> I was never glad with size_t string lengths and told about it.
>
>>
>>
>> > Do you provide support for all other unrelated proposals when you offer
>> > your
>> > own?
>>
>> I do not understand the question, what do you mean?
>
>
> I mean that when you develop something big, you have to be concentrated on
> the goals you are going to solve and not on compatibility with others
> proposals.

Right, but this is possible to achieve  by cooperating with the
authors of other proposals. Early and well organized proposals
minimize the pain for other developers while maximizing the chance of
success.


>> However, about support, we do offer support for almost every proposal,
>> be for testing, build fixes, etc. Pro actively in most cases, whether
>> it is in our priorities list or not. My reasoning here is pretty
>> simple, a stable PHP, for all supported platform or configuration is
>> critical for the success of PHP. Cooperation too.
>>
>> > Lets think how to integrate them. I propose doing it in two steps
>> > (measuring
>> > the performance and memory consumption difference).
>> > If the degradation is going to be invisible, I won't object.
>>
>> The numbers are available already, using master and 5.5-5.6. We
>> obviously do not have numbers using your patch but I do not think the
>> delta will be any different.
>
>
> phpng completely changes zval structure and reduces overhead of some
> subsystems, so the numbers might be different.

They will be different, no doubt here, but there should not be that
much differences from a relative point of view.

However I do not think I can go to my team and asked to do that from
scratch based on a work in progress effort (even a very good one :).
The more I look at it the more I think it is easier and faster to
merge the 64bit and then adapt the other one, if accepted (for both
proposals).

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org