Hi, Emeric
got it.
Thanks a lot
Mike
At 2017-12-21 18:19:50, "Emeric Brun" wrote:
>Hi Mike,
>
>Thierry is right, 4096 rsa key computation have clearly an heavy CPU cost.
>In our internal benchmark we notice:
>Using one process of haproxy on one core of i7-4790K CPU @ 4.00GHz we
Hi Mike,
Thierry is right, 4096 rsa key computation have clearly an heavy CPU cost.
In our internal benchmark we notice:
Using one process of haproxy on one core of i7-4790K CPU @ 4.00GHz we reach 170
con/s (comparatively 1350 con/s using 2048 rsa key).
Usually this CPU usage isn't so high becau
Hi, JohanThanks a lotMikeSent from my HuaWei mate9 Phone 原始邮件 主题:Re: Haproxy SSl Termination performance issue发件人:Johan Hendriks 收件人:haproxy@formilux.org,hongw...@163.com抄送:Op di 19 dec. 2017 om 16:16 schreef hongw...@163.com Hi, Thierry.Thanks again.One more quest
Hi, Thierry.Thanks again.One more question about you talking about, can i just think like this way: assume we got a 8core cpu, we use 7 of them for ssl termination and one is for http forward? If it is, is there any document for this soulution?Thanks a lotMike 原始邮件 主题:Re: Haproxy S
Hi,ThierryMany thanksMike发自我的华为手机 原始邮件 主题:Re: Haproxy SSl Termination performance issue发件人:Thierry Fournier 收件人:Mike G 抄送:Haproxy Ok, you’re using HAProxy as SSL offloading. HAProxy is one of theright solutions for doing this. You’re performance problem is notdue to HAProxy, each co
Hi,Thierrygot it. Thanks!By the way, may I ask the ssl termination is best solution for this kind of job?Many thanksMike 原始邮件 主题:Re: Haproxy SSl Termination performance issue发件人:Thierry Fournier 收件人:Mike G 抄送:Haproxy Hi,I gues that 130 is 130 SSL requests per seconds ?SSL is a very
6 matches
Mail list logo