On Fri, 20 Apr 2001, Paul J. Reder wrote:
> I'm sure that there are some aspects of mod_include that can be improved,
> but the fact of the matter is that a filter that looks at every byte across
> buckets and brigades is going to slow things down. With 2.0 admins will
> need to do a more judicious job of bringing filters into play (like not
> running all .html and .shtml files through mod_include).
Clearly.
> > I also have some truss output for these, and I'll put them on the site
> > if anyone wants to see what is going on.
>
> I would love to see any performance or profiling information that you have.
> The more info, the better the solution.
Still on my plate (I'll get it done soon, I swear) is the new memory
allocation scheme for buckets, which should reduce many of the problems
that filters/bucket brigades in general are currently having
performance-wise. I'd not be surprised at all if a truss of what's there
currently shows lots of time spent in malloc/free, especially on a
threaded MPM. We've seen it before, and I've no reason to believe that
this is any different. With threading enabled, the poor buckets code
spends half its time trying to acquire mutexes. <sigh>
--Cliff
--------------------------------------------------------------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
