On Dec 10, 2007 10:42 PM, Stefan Fritsch [EMAIL PROTECTED] wrote:
Yes, that works as well. I wanted to avoid calling APR_BRIGADE_PREPEND
when the temporary brigade is empty. But I don't really know whether
APR_BRIGADE_PREPEND is so expensive that this makes sense. An
alternative would be to
-Ursprüngliche Nachricht-
Im Auftrag von Justin Erenkrantz
Gesendet: Dienstag, 11. Dezember 2007 11:05
An: dev@httpd.apache.org
Betreff: Re: Apache memory usage
On Dec 10, 2007 10:42 PM, Stefan Fritsch wrote:
Yes, that works as well. I wanted to avoid calling
-Ursprüngliche Nachricht-
Von: Stefan Fritsch
Gesendet: Montag, 10. Dezember 2007 22:43
An: dev@httpd.apache.org
Betreff: Re: Apache memory usage
On Sunday 09 December 2007, Ruediger Pluem wrote:
But I think your patch to server/protocol.c can be done much
simpler. Can you
On Sunday 09 December 2007, Ruediger Pluem wrote:
But I think your patch to server/protocol.c can be done much
simpler. Can you try the following and let us know if this helps as
well:
Index: server/protocol.c
===
---
Hi,
On Monday 03 December 2007, Stefan Fritsch wrote:
But I found two locations where the creation of a new brigade could
be avoided:
- In buffer_output()/ap_old_write_filter(), it is possible to keep
the brigade around and reuse it after the next flush.
- In ap_http_chunk_filter(), a new
On 12/09/2007 10:03 PM, Stefan Fritsch wrote:
Hi,
On Monday 03 December 2007, Stefan Fritsch wrote:
But I found two locations where the creation of a new brigade could
be avoided:
- In buffer_output()/ap_old_write_filter(), it is possible to keep
the brigade around and reuse it after
Hi,
there is still the problem that during a request, many bucket brigades
being created which are only cleaned up after the request is
finished, see
http://issues.apache.org/bugzilla/show_bug.cgi?id=23567 . There was
some discussion about retaining ownership of a brigade when