Great! It's about time someone gave us something newer than the old Sean Adams standby
I think you've done a great job! Here are a few constructive comments, I hope you will take them in the spirit with which they are intended.
- I would move the detailed examples to the bottom of the page. The 324GB question and related topics are much more relevant to your core audience, and I'd hate to see some of them give up before they get there.
- "How many gigabytes are in a megabit/sec?"
Consider going the other way as well, i.e. "My host says I transferred X GB last month. What is the 95th percentile equivalent?" I would emphasize that there is no reliable way to make this determination without a corresponding value for throughput during the same period.
- "To determine the number of gigabytes transferred you simply multiply the mean utilization, represented on the example graph at 3.11 Mbit/sec, by the time span of the billing period."
Consider explaining exactly what mean utilization is. I think this is particular important given most out-of-the-box metering software configurations display 'average' values.
- "That 324GB per Mbit/sec figure is roughly accurate for a 31 day calendar month of mean utilization,"
I think it would be beneficial to emphasize you're referring to 31 days of *continuous 1mbps* mean utilization, being sure to tie back to the previous definition of mean utilization.
- "which tells us that the example traffic is about 56% efficient vs a 100% efficient traffic profile, where the mean utilization is equal to the 95th percentile utilization"
Maybe it's just me, but I think it's easy to miss you're actually defining 100% efficient here.
- "My host offers per-GB and 95th percentile billing. Which is better?"
The entire answer hinges on your one example, no doubt appropriately chosen for this specific application

. While I agree your analysis & result is orders of magnitude better than the oft-quoted 324 per 1mbps reference, in the interest of full disclosure it would probably be a good idea to clarify that the 190GB cited could be considerably higher or lower based on the reader's specific circumstances. That of course would then impact the subsequent ratio results of 0.56 and 1.76, respectively. Not a big deal of course, I would just hate for those values to become ingrained as defacto standards without going further to clarify that they are based on a specific (albeit typical) observation.
- "Example Customer Equivilant Costs"
Equivalent
Again, great job. Thanks for taking the time to post this since it's sure to be referenced at least once a week on this forum alone
Brandon