2

The Yahoo Developer Best Practices recommend using multiple hosts (host1.company.com, host2.company.com, etc..) as a way of overcoming a webbrowsers built in limitation of only issuing two concurrent requests per domain.

Please gloss over this backgrounder for more information.

Before I begin, don't be confused into thinking that I am talking about "DNS performance". I'm not. I'm only talking about overcoming a browsers' built-in throttling mechanism.

So, how do I properly implement a HTTPS-only website with regard to parallel requests?

This is a logical question because every new HTTPS request will incur setup and teardown costs. This will impact performance in proportion to how many SSL/TLS connections opened.

The factors that affect the performance of a SSL/TLS connection include

So if I think further about the dependencies involved, that makes me ask these questions:

Does my certificate choice affect performance when using many DNS domains?

Does the server configuration affect performance when using many DNS domains?

example:

Suppose a web browser downloads content from 10 different subdomains, it potentially has to set up each SSL session from scratch. That would mean there could be a significant delay in getting the first page to load.

  • Would first-page load of PFS perform better or worse than AES vs RC4? What about the second page?

  • Can a wildcard certificate (or one with different Subject Alternative Names) allow me to use many domains with many domain names? Will this solve the performance problem?

Improve this question
4

3 Answers 3

Reset to default
0

I don't think this covers all your questions but here is a link to HTTPS Performance Tuning and another for Overclocking SSL

Improve this answer
0

Browser connection limits are more of an issue for older browsers (e.g. ie 7 and earlier) that had a limit of two connections per host name. Modern browsers use up to 6 connections per hostname.

In fact, sharding across multiple domains can end up being slower with modern browsers because of the additional overhead of setting up each connection. It would be worth running some tests on target browser versions before deciding whether to put resources on different host names.

If you do decide to use multiple host names with SSL then the easiest way to do that is to use a wild card SSL certificate as described in this blog post:

http://blog.httpwatch.com/2011/01/28/top-7-myths-about-https/

Improve this answer
0

With regard to parallel requests... Have you looked at the benefit that a script loader can provide? Assuming your site uses javascript and lots of images. Like most do these days!

Per the LABjs folks:

In addition to loading scripts in parallel, scripts loaded through LABjs no longer block page resource downloads (images, CSS). This will generally lead to significant decreases in page-load time (often 2x - 3x faster).

Cheers

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .