HTTPS Load Test

[Das, Jagannath]

Thanks Edward.

What is the expected ratio of CPU Usage when HTTPS is enabled at Nginx ? How is the ratio affected when we enable persistent HTTP
Support?

Folks from nginx or who have already bench marked may help here and can point me to useful links on web.

From: Edward Hibbert <edward at ehibbert.org.uk<mailto:edward at ehibbert.org.uk>>
Reply-To: "nginx at nginx.org<mailto:nginx at nginx.org>" <nginx at nginx.org<mailto:nginx at nginx.org>>
Date: Thursday, January 8, 2015 at 4:00 PM
To: "nginx at nginx.org<mailto:nginx at nginx.org>" <nginx at nginx.org<mailto:nginx at nginx.org>>
Subject: Re: HTTPS Load Test

Bombard is a useful wrapper round siege.

I've had trouble using siege with more than a couple of thousand connections - crashes with buffer overflow.  I've not tried to debug this yet but would be interested in other people's experiences.

On Thu, Jan 8, 2015 at 10:16 AM, basti <black.fledermaus at arcor.de<mailto:black.fledermaus at arcor.de>> wrote:
You can try "siege".
In the past I have take the access log to create a list of urls to be
used by siege.

Regards,
Basti

On 08.01.2015 11:06, Das, Jagannath wrote:
> Hi Folks,
>    I am trying to get some performance numbers on nginx  by sending
> HTTP and HTTPS requests.  My aim is to check the ratio of CPU usage,
> connections/sec across HTTP and HTTPS requests.
>
> In the process, I need to verify certain certificates/keys needed for
> SSL . Are there any tools which can help in generating the load in the
> following conditions:
>
>  1. Keepalive/Persistent HTTP client support.
>  2. Options to verify the certificates/keys/CA chain certs.
>
>
> Thanks,
> Jagannath
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org<mailto:nginx at nginx.org>
> http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx at nginx.org<mailto:nginx at nginx.org>
http://mailman.nginx.org/mailman/listinfo/nginx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20150108/c28b9c1e/attachment.html>