|
Home > Archive > Apache Server configuration support > January 2007 > SSL performance question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SSL performance question
|
|
| tgh003@gmail.com 2007-01-06, 8:11 pm |
| I have a question about SSL and am hoping someone can clarify.
My setup: We run Apache 2.0 on FreeBSD w/ Mod SSL (we use a wildcard
certificate so *.mycompany.com).
I have a web application that makes pretty heavy use of Javascript,
couple of style sheets, and several other image assets. Probably a
total of ~30 assets per page (images, style sheets, and script files).
I understand that spreading these assets over several subdomains can
significantly reduce the client side load time. (this is because
pipelining isnt turned on the major browsers so the maximum number of
assets the browser can download simultaneously is 2, so if you spread
the load amongst several domains you can download more assets
simultaneously).
Does this benefit still hold true if you are on a SSL connection? If I
spread the assets across say 4 subdomains (subdomain1.mycompany.com,
subdomain2.mycompany.com, etc...) does each of these connections need
to perform a new SSL handshake for every page thus negating the
benefit? Or is the first request just going to be slower because it
does indeed need to make 4 separate ssl handshakes but the rest of the
session (all subsequent page loads) is faster? Or is there a way to
handshake on the base url such as https://*.mycompany.com thus making
all subsequent requests faster?
Basically I am trying to make all the pages load faster. Any thoughts
are appreciated.
| |
| Davide Bianchi 2007-01-06, 8:11 pm |
| On 2007-01-05, tgh003@gmail.com <tgh003@gmail.com> wrote:
> I have a web application that makes pretty heavy use of Javascript,
> couple of style sheets, and several other image assets. Probably a
> total of ~30 assets per page (images, style sheets, and script files).
>
> I understand that spreading these assets over several subdomains can
> significantly reduce the client side load time. (this is because
hu? run it again? if the browser doesn't load more than 2 'assets'
at a time, the fact that he is loading them from different 'domains'
(all pointing to the same IP) or not should not make any difference.
> Basically I am trying to make all the pages load faster. Any thoughts
> are appreciated.
Enable caching then, have them loading from memory instead of read
from disk, use compression to send less data, check if you have a
bottleneck in the number of connections you accept (some DOS prevention
sometimes turn out to be a DOS on his own).
Davide
--
Damn, this sounds just like my NT machine here at work. Also, it was
shaped sort of like a big gonzo potato-peeler. -- Carl Jacobs
Oh, it's a Compaq... -- Henrik
| |
| Ottavio Caruso 2007-01-06, 8:12 pm |
| tgh003@gmail.com wrote:
> I understand that spreading these assets over several subdomains can
> significantly reduce the client side load time. (this is because
> pipelining isnt turned on the major browsers so the maximum number of
> assets the browser can download simultaneously is 2, so if you spread
> the load amongst several domains you can download more assets
> simultaneously).
Is this true? Any documentation to back it up?
Maybe if you spread the load (static and dynamic pages) among different
machines...
Ottavio
http://www.pledgebank.com/boycottvista
|
|
|
|
|