https://bz.apache.org/bugzilla/show_bug.cgi?id=56984
Yann Ylavic <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|REOPENED |RESOLVED --- Comment #12 from Yann Ylavic <[email protected]> --- (In reply to gmoniker from comment #11) > > I still think though that there are some concerns about this when you have > requests with a long runtime, high pool usage and very small ack-like > response. It could take several requests before any output gets sent back > and memory gets cleared. The maximum number of pipelined responses is 5 (see ap_core_output_filter()'s MAX_REQUESTS_IN_PIPELINE), and when this limit is reached, all 5 requests are destroyed at once. > > Also apache modules that didn't get updated to take this into account can > misbehave as is now painfully clear. Not only can they have issues with pool > cleanups not having run, but also with reentry of handlers that are also > registered for output filters and respond to an EOS bucket of a previous > request while processing a follow-on request. Modules switching from httpd < 2.4 to >= 2.4 should normally take the new features into account (eg. pipelining), otherwise no major advancement would be possible on the httpd side. > > Most of the time I am just the custodian of a webserver and am most > concerned with it functioning reliable and not having the highest possible > performance. So I guess what I should be asking is, can we make it a feature > request to have the option of configging Apache 2.4 to do a flush after each > client request? Maybe MAX_REQUESTS_IN_PIPELINE could be configurable, or/and proxy/cgi(/php?) modules improved to flush when further responses take time to come (mod_proxy_http does that already IIRC)... That's another story though, and we should discuss this on user@ (or dev@) mailing list, or create another bugzilla ticket (enhancement) for this. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
