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
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
