<div class="gmail_quote">On Thu, Nov 4, 2010 at 9:13 AM, Matthew Steven <span dir="ltr"><<a href="mailto:matthew@geniusweb.com">matthew@geniusweb.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Unless your server is very weak on hardware and/or network resources it should be faster than that.<br>
<br>
'ab' can give you a more realistic idea of real page performance though. Running 'ab' to fetch my mythweb page across the lan 1000 times took 0.028 seconds, average time per request being around 0.284ms. And that's a weak piece of special-purpose hardware.<br>
<br>
The "page speed" firebug extension is also handy to view a page in detail.<br>
<br>
You could use a SSL accelerator card or appliance if you are certain that there are no more things you can do on the server to speed up your page. Is deflate enabled for html content? Did you verify that xcache is working properly? Does it get faster on the second load?<div>
<div></div><div class="h5"><br>
<br></div></div></blockquote><div><br></div><div>Great tips. It looks like for my SSL content on this server I'm at about 350ms unless something can be done on the server side. I'm currently in dev mode and my staging server is on the weak side. I will look at this more closely when I'm ready to go live.</div>
<div><br></div><div>I will give nginx a try but on my staging server I'm skeptical that running nginx + apache will help much. Maybe if I use nginx + fastcgi (no apache).</div></div><div><br></div><div>What kinds of latency do you think is realistic from a good server doing SSL? Maybe 350ms is the norm?</div>
<br>-- <br>Matthew Nuzum<br>newz2000 on freenode, skype, linkedin, <a href="http://identi.ca" target="_blank">identi.ca</a> and twitter<br><br>"An investment in knowledge pays the best interest." -Benjamin Franklin <br>
<br>