On Sat, 2014-02-15 at 11:22 +0100, Sebastiano Vigna wrote:
Something happened from HttpClient 4.3.1 to 4.3.2.
All of a sudden, we are seeing an immense amount of CPU spent into inflating
compressed HTTP responses. We were experimenting 5000 pages/s two months
ago, but less than 1200
On 15 Feb 2014, at 12:47 PM, Oleg Kalnichevski ol...@apache.org wrote:
The problem mostly likely has been introduced by HTTPCLIENT-1432 [1]. I
reviewed the patch once more and could not find anything obviously wrong
with it. Try reverting the changes introduced by HTTPCLIENT-1432 and see
On Sat, 2014-02-15 at 17:06 +0100, Sebastiano Vigna wrote:
On 15 Feb 2014, at 12:47 PM, Oleg Kalnichevski ol...@apache.org wrote:
The problem mostly likely has been introduced by HTTPCLIENT-1432 [1]. I
reviewed the patch once more and could not find anything obviously wrong
with it. Try
