Re:Optimizing HTTPS performance
by Ono-Sendai on Sunday January 31, 2016 @02:10PM
(#11007529)
I tested it with some of my own code, 8 threads making requests to my server at localhost.
Does this program 'wrk' re-establish a connection for each request, or is it re-using them?
wrk[1] does appear to reuse a connection for each request.
Any idea how HTTPS manages to have a significantly higher throughput? At first blush this doesn't quite pass the sniff test - it looks like there's another factor in play here.
That's probably because the response to this particular https URL is larger; http on this server simply redirects to https and is therefore a smaller response.
Not that this matters here; the top level comment measured requests per second, not bytes per second. If anything, the smaller response for http would give http an advantage in this comparison.
When measuring on one of my servers that exposes both HTTP and HTTPS, there doesn't appear to be any significant difference.
HTTP:
HTTPS: