Hi Grant,
On 03/28/2017 07:38 AM, Willy Tarreau wrote:
> Hi guys,
>
> On Mon, Mar 27, 2017 at 02:57:38PM -0700, Grant Zhang wrote:
>>> sign verify sign/s verify/s
>>> rsa 2048 bits 0.000745s 0.000034s 1342.9 29050.3
>>
>> Hmm, the numbers are less than what I've seen:
> (...)
>
> This is an atom C2518 and it seems that --disable-prf has cut the performance
> in half. We should receive a 8920 soon.
>
>>> Stopping the injection, the haproxy process continue to steal cpu doing
>>> nothing (top shows ~50% of one core, mainly in user):
>> Hmm, an idle haproxy process with qat enabled consumes about 5% of a core in
>> my test. 50% is too much:-(.
>
> In theory it should not consume anything anymore if it has nothing to do,
> so maybe the 5% you observed will help understand what is happening.
I've just noticed 50% cpu usage directly at start-up if we enable the engine (w
or wout ssl-async):
global
tune.ssl.default-dh-param 2048
ssl-engine qat
# ssl-async
listen gg
mode http
bind 0.0.0.0:9443 ssl crt /root/2048.pem ciphers AES
redirect location
R,
Emeric
