<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div></div><div><br></div><div><br><div><div>On Jun 17, 2008, at 12:37 PM, Wald Lisa wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><b>Web Team et al.-</b><div><br></div><div>This email is just for your information. If you aren't interested in the website traffic and how Akamai bills us for it, you can delete this.</div><div><br></div><div>Lorna Schmid, Judy Ferrier, and I had a conference call with Todd Aikers at Akamai list week to learn how Akamai bills us for services and what our options are for the future. This is a summary of what we learned.</div><div><br></div><div><b>AKAMAI FEE ALGORITHM</b></div><div>The annual contract with Akamai is 420K. The Earthquake Hazards Program has been paying 120K of the bill, while E-web has been paying 300K. The contract covers:</div><div><br></div><div><a href="http://www.usgs.gov">www.usgs.gov</a></div><div>earthquake.usgs.gov</div><div>quake.wr.usgs.gov</div><div>pasadena.wr.usgs.gov</div><div>neic.usgs.gov</div><div><br></div><div>We basically pay for bandwidth per month. We are allotted 30mbits/sec average per month using something called the 95/5 algorithm which has something to do with 95%. In addition we have 400mbits for the entire year that we can draw from if we go over the 30mbits/sec in any month (termed "bursting"). We are not charged for super-bursting until we reach 4 times our monthly allotment (30 mbit/sec x 4) which is 120 mbits/sec. At that point we're charged $0.02 per mbyte over the 120mbits. Note that the units are different, and we don't know exactly how this part works yet. In any case, we have not had any superbursting charges since this algorithm was put into place (or we should not have had any, in any case, although Lorna thinks we may have paid for superbursting when we weren't supposed to in the past).</div><div><br></div><div><b>EHP AKAMAI USAGE</b></div><div>In February of this year, our Akamai usage went over 30mbits/sec for the first time; it was 40+ in Feb, 50+ in April, and almost 70 in May. Most of the increase was from the EHP website, but we're still trying to determine if it is due to simply increasing traffic due to recent earthquakes, or if there is a new or larger file that has caused the significant increase. Since we've been making alot of changes to configurations on the Akamai end and on our end, it's difficult to pinpoint the cause. The most recent config change was made at the beginning of June, so we will have to wait until the end of this month to see the significance of the latest change.</div><div><br></div><div><b>BOTTOM LINE</b></div><div>E-web wants the Earthquake Hazards Program to pay for the percentage of Akamai services that we're using when the contract is renewed (or re-bid) soon, which will be significantly more than 120K, since we use approximately 90% of the service. No matter who ends up paying for the service, we need to determine the cause of our rising bandwidth and configure our Akamai usage to minimize this number. However, if the increase is due simply to increasing web traffic, there is really nothing we can do aside from optimizing our file sizes, which we have done with some files, and continue to investigate for others.</div><div><br></div><div>I am currently do some log analysis with our web traffic stats, but nothing is jumping out at me as the single cause of the increasing bandwidth. I'll be looking into "last mile compression" this week which could buy us a huge savings all the way around.</div><div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>- Lisa</div><div>------</div><div><br class="webkit-block-placeholder"></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"> </div><br></div></div>_______________________________________________<br>EHPweb mailing list<br><a href="mailto:EHPweb@geohazards.usgs.gov">EHPweb@geohazards.usgs.gov</a><br>https://geohazards.usgs.gov/mailman/listinfo/ehpweb<br></blockquote></div><br></div></body></html>