Local

..:: Home
..:: Legal
..:: Contact
..:: About
..:: RSS
..:: Log in

Links

..:: Fake Bill Gates
..:: Tap the Hive

A Random Quote

"Here's to the crazy ones. The misfits. The rebels. The trouble-makers. The round heads in the square holes. The ones who see things differently. They're not fond of rules, and they have no respect for the status-quo. You can quote them, disagree with them, glorify, or vilify them. But the only thing you can't do is ignore them. Because they change things. They push the human race forward. And while some may see them as the crazy ones, we see genius. Because the people who are crazy enough to think they can change the world, are the ones who do." -- Jack Kerouac

Archive for the ‘Server Administration’ Category

5-9s Explained

Friday, October 3rd, 2008

In talking about server uptime the discussion has come up as to what it means to say “5-9s” or “6-9s”.  Each has a VERY specific meaning in regards to the average percentage uptime in any given 365 day period.  5-9s means a 99.999% uptime (there’s 5 9s).  That’s 364.99635 days, or better put only 5 minutes and roughly 15 seconds of downtime in the aggregate over 365 days.

If you’ve ever had a webserver that got hit by the slashdot/digg/fark/reddit effect, then you’d know that your host probably hates you for destroying their 5-9 uptime.  On one of my other sites, I had an article that was frontpaged on reddit for a few hours and linked to a good number of popular news sites.  In 48 hours, I recorded over 150,000 unique visits, and all three of my tracking mechanisms were down for an extensive period.  The traffic brought down the entire server for about 2 hours, and that was after the page was changed to static HTML and I dumped a ton of the markup on it to remove linked js libraries and images.  My host moved me to a much less used and tragically faster server as a result, and the hosting packages is now one of the best around for non-colo.  In the end, I learned a lot about servers under high load.

Now, here’s a table to help understand exactly how much downtime is allowed before the threshold is breached.

short name uptime percentage/100 minimum uptime max downtime downtime unit
0.75 273.75 91.25 days
0.76 277.4 87.6 days
0.77 281.05 83.95 days
0.78 284.7 80.3 days
0.79 288.35 76.65 days
0.8 292 73 days
0.81 295.65 69.35 days
0.82 299.3 65.7 days
0.83 302.95 62.05 days
0.84 306.6 58.4 days
0.85 310.25 54.75 days
0.86 313.9 51.1 days
0.87 317.55 47.45 days
0.88 321.2 43.8 days
0.89 324.85 40.15 days
0.9 328.5 36.5 days
2-9s 0.99 361.35 3.65 days
3-9s 0.999 364.635 8.76 hrs
4-9s 0.9999 364.9635 52.56 min
5-9s 0.99999 364.99635 5.256 min
6-9s 0.999999 364.999635 31.536 sec
7-9s 0.9999999 364.9999635 3.1536 sec
8-9s 0.99999999 364.9999964 0.31536 sec
10-9s 0.999999999 364.9999996 0.031536 sec

Note that the units on the far right column change.  For a day unit, the max downtime decimal is base 24 in hours.  So for instance, 75% uptime is 91.25 days, but .25 days is 6 hours, so it’s 91 days and 6 hours.  At 3-9s and below, the decimal is base 60, so the max downtime is 8 hours 45 minutes and 36 seconds for 3-9s.

If you’re really a stickler, you have to pay attention to how the service provider phrases the uptime claim.  If they say “we provide better than 99.999% uptime” (as opposed to “we provide 99.999% uptime or better”), that means there’s LESS than but not equal to 5.256 minutes of downtime in a 365 day period.  It’s really just an inclusive/exclusive question on the range of  numbers.

As for choosing the right level of service for your site, it really comes down to number crunching and how much your site actually brings in.  Take, for example, the blog BoingBoingFederated Media sells out a 125×125 ad spot on the site for $7.00 CPM.  With 7.83 million monthly page views, that means the site gets a steady 3 hits per second.  Even if we say that the site only has a single 125px square for ad revenue on each page to generate revenue (though it has more), the site brings in AT ABSOLUTE VERY LEAST 2.1 cents per second on average.  The difference between 6-9s and 7-9s is about 28 seconds, so you can see that at only 2.1 cents per second, that extra 9 only brings in another 60 cents.  Now because we can only compare the bottom end of the income (as opposed to the top end of the income) to the service costs we can only say what might be a good deal - not what would be a bad deal (with more data on actual income per second, we could determine to the second how much guaranteed uptime they should buy).  The difference between 6-9s and 7-9s is only about 28 seconds.  So if upgrading from 6-9s to 7-9s costs 60 cents or less (incredibly unrealistic), we can safely say that’s a good deal.  But we’re not sure 6-9s is even worth it, so lets go a little farther down the uptime list to 1-9 vs 2-9s.  At 1-9, that’s 36.5 days of downtime.  In 36.5 days downtime at 2.1 cents per second, the site misses out on at least $66,225.60.  At 2-9s, the site misses out on $6,622.56.  Pragmatically, if the cost between going from 1-9 to 2-9s is less than the difference ($59,604.04), then it’s definitely worth it for the company to upgrade service from 1-9 to 2-9s.

For companies that use their site solely for referrals that convert into a sale or service contract, 4-9 or 5-9 service levels (which are rather common) are typically more than enough.  But, in very high end enterprise systems like investment companies, stock exchanges, and multi-billion record inventory databases where the income per second is measured in the hundreds or thousands or even millions of dollars, even 15-9s uptime might be worth the fees.