Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
From: Jim Jagielski <jim@jaguNET.com>
Message-Id: <200206082306.TAA19677@devsys.jaguNET.com>
Subject: Re: [PHP-DEV] Re: PHP profiling results under 2.0.37  Re: Performance
 of Apache
To: jwoolley@virginia.edu (Cliff Woolley)
Date: Sat, 8 Jun 2002 19:06:23 -0400 (EDT)
Cc: dev@httpd.apache.org, php-dev@lists.php.net
Reply-To: jim@jaguNET.com
In-Reply-To: 
 <Pine.LNX.4.44.0206081359450.23141-100000@deepthought.cs.virginia.edu> from
 "Cliff Woolley" at Jun 08, 2002 02:03:21 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Cliff Woolley wrote:
> 
> >
> > It looks like "unbuffered" PHP output in 1.3 is benefitting from the
> > httpd's own buffering.  And "unbuffered" output in 2.0, in contrast,
> > is really, really not buffered, because of the flush buckets inserted
> > by php_apache_sapi_ub_write.
> 
> 
> If the unbuffered write really *is* allowed to be buffered (wtf?), then by
> all means we should change to using apr_brigade_write() there instead of
> the flush() buckets.
> 

You say buffered, I say unbuffered, let's call the whole thing off... :)

Seriously though, +1
-- 
===========================================================================
   Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
      "A society that will trade a little liberty for a little order
             will lose both and deserve neither" - T.Jefferson