On 08/29/2018 10:49 AM, Christophe Jaillet wrote:
> Ok, it is trickier than I thought.
>
> On 2018/08/29 07:55:04, Ruediger Pluem wrote:
>>
>> 2. As the error handling is a stack I think it is a valid use case for
>> another consumer of openssl to check for the
>>error later and not dire
Ok, it is trickier than I thought.
On 2018/08/29 07:55:04, Ruediger Pluem wrote:
>
> 2. As the error handling is a stack I think it is a valid use case for
> another consumer of openssl to check for the
>error later and not directly like e.g. with errno.
>
but in this case, haven't we al
Just for interest ran my h2 load tests on trunk/2.4.x unpatched and with
commenting ERR_clear_error(); in ssl_engine_io.c
On my Mac I see no differences, really. trunk used openssl 1.0.2o and 2.4.x had
1.0.2l:
> h2load -i gen/load-urls-1.txt -n 20 -t 4 -m 100 -c
trunk
raw, 128 clients:
On 08/29/2018 09:37 AM, Christophe Jaillet wrote:
> Pure speculation:
>
> Actually we ERR_clear_error unconditionally so that in case of error, we can
> safely call SSL_get_error.
>
> Doc says:
> << >>
> ERR_get_error() returns the earliest error code from the thread's error q
nvl005 (be patient)
> >> Completed 20 requests
> >> Completed 40 requests
> >> Completed 60 requests
> >> Completed 80 requests
> >> Completed 100 requests
> >> Completed 120 requests
> >> Completed 140 requests
>
t; Completed 180 requests
>> Completed 200 requests
>> Finished 200 requests
>>
>>
>> Connection Times (ms)
>> min mean[+/-sd] median max
>> Connect: 0 0 2.1 0 208
>> Processing: 0 17 20.3 1
otal: 0 17 20.4 10 285
>
> Percentage of the requests served within a certain time (ms)
> 50% 10
> 66% 16
> 75% 23
> 80% 28
> 90% 44
> 95% 59
> 98% 79
> 99% 94
> 100%285 (longest request)
>
>
Hello,
On 2018-08-28 10:54, William A Rowe Jr wrote:
> As we unwind various regressions and breakage, one non-lethal but
> somewhat horrid report stands out. Eric correctly tied it to the patch
> applied for https://bz.apache.org/bugzilla/show_bug.cgi?id=62590 in the
> 2.4.24 timeframe.
I'd like
-- Forwarded message --
From:
Date: Mon, Aug 27, 2018 at 9:11 AM
Subject: [Bug 62590] performance drop after moving from apache 2.2 to
apache 2.4
To: b...@httpd.apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=62590
--- Comment #1 from paolo ---
After some debug-session I fou
