Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:281
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <3E80CD8D.7080505@holsman.net>
Date: Tue, 25 Mar 2003 13:43:41 -0800
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: internals@lists.php.net
References: <200303251611.12012.ilia@prohost.org>
In-Reply-To: <200303251611.12012.ilia@prohost.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Preliminary Apache 2 benchmarks
From: lists@holsman.net ("lists@holsman.net")

resend due to 30k issue.


> Attached is the patch (ap2.txt) that prevents AP2 handler from constantly 
> flushing the data as soon as it is passed. As you can see in the benchmarks 
> this more the doubles the performance when many writes occur. I am hoping Ian 
> can explain the need for this flush, since without it the code would be 
> clearly faster.

in the general (like 99.9%) of the case you don't need to flush.
I think disabling it will be a good thing.

the original version I committed actually waited until the entire page was parsed
before sending anything up the chain.

this is slightly different to what it currently does, and I'll try to see if I can see a difference 
in this approach (compared to sending the buckets up the filter chain)

if there is a difference, I'll add a new directive to buffer the response up.
> Ilia
>