Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36520
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain prohost.org from 209.85.132.251 cause and error)
Cc: Marcus Boerger <helly@php.net>,
 PHP Internals List <internals@lists.php.net>
Message-ID: <64B4F6F2-B123-461F-99A1-EB10502B671A@prohost.org>
To: Dmitry Stogov <dmitry@zend.com>
In-Reply-To: <47E8D7FC.7020409@zend.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 25 Mar 2008 16:39:41 -0400
References: <47E8D19C.6090608@zend.com> <505001029.20080325112757@marcus-boerger.de> <47E8D7FC.7020409@zend.com>
Subject: Re: [PHP-DEV] re2c scanner issue
From: ilia@prohost.org (Ilia Alshanetsky)

This is without an opcode cache I presume?


On 25-Mar-08, at 6:46 AM, Dmitry Stogov wrote:
> Sorry, but I didn't store benchmarks before re2c patch so I can just  
> compare PHP_5_3 and PHP_5_2.
>
> Drupal 20% faster
> Qdig 2% faster
> typo3 30% faster
> wordpress  15% faster
> xoops 10% faster
>
> Not all the speedup caused by re2c scanner, but it makes significant  
> part of it.
>
> Thanks. Dmitry.
>
>
> Marcus Boerger wrote:
>> Hello Dmitry,
>> Tuesday, March 25, 2008, 11:19:08 AM, you wrote:
>>> Hi Marcus,
>>> The ext/tokenizer/tests/token_get_all_variation17.phpt is probably  
>>> the
>> There are probably more changes coming so there is not so much need  
>> to
>> change this part right now.
>>> last broken test. It has a memleak. I am not trying to fix it  
>>> because you should know it much better, also re2c scanner is not  
>>> ported to HEAD yet and you may keep changes that must be ported.
>> Yep we're aware of this. Right now Scott is doing the MFB to HEAD  
>> part and
>> last time I talked with him he made pretty good progress. I updated  
>> a lot
>> of stuff in re2c to give myself more freedom in how to address the  
>> task of
>> bringing back multibyte support back in. I also started on the PHP  
>> side and
>> fixed quite a bunch of issues in the multibyte code so far. The  
>> good news
>> is that my normal build still works as expected.
>>> BTW PHP_5_3 became faster. Good work!
>> Good to hear from others. Did you do any profiling you could share?
>> Best regards,
>> Marcus
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

Ilia Alshanetsky