Upstream SSL IIS Performance

[Francis Daly]

On Sun, Aug 19, 2012 at 07:55:07PM -0400, d2radio wrote:

Hi there,

> GET /client/javascript/libraries/query-string/2.1.7/query-min.js HTTP/1.1"
> 200 upstream 0.040 request 0.046 [for reversproxy via 172.25.50.203:80]
> 
> GET /client/javascript/libraries/query-string/2.1.7/query-min.js HTTP/1.1"
> 200 upstream 0.234 request 0.243 [for reverseproxy via 172.25.50.203:443]

time curl https://172.25.50.203/client/javascript/libraries/query-string/2.1.7/query-min.js

Does it show about 200 ms like above, or about 20 ms like firebug showed?

I suspect that the 200 ms is due to the ssl session being established
afresh for each request, while firebug is piggy-backing on a previous
request.

(You could test this by starting firebug and making sure that the
very first https query is for this url, and seeing how long it takes.)

> Do I have any options for improving the https response
> performance with the upsteam IIS server? Apart from talking to it via HTTP?

Untested by me, but: do you see any difference when you include the
configuration at http://nginx.org/r/keepalive ?

That might allow re-use of the ssl session across http requests.

	f
-- 
Francis Daly        francis at daoine.org