Performance Metrics - 2010
Percentage of time that a request for a page is returned within three seconds from on campus (target: 99.9%)
Month | % |
---|---|
Jan '10 | 99.89% |
Feb '10 | 99.90% |
Mar '10 | 99.86% |
Apr '10 | 99.91% |
May '10 | 99.93% |
Jun '10 | 100% |
Jul '10 | 99.99% |
Aug '10 | 100% |
Sep '10 | 99.99% |
Oct '10 | 99.99% |
Nov '10 | 100% |
Dec '10 | 100% |
Availability off-campus, as measured by Pingdom.com (30 second timeout, from at least 2 out of 10 locations ) (no target set)
Month | % |
---|---|
Jan '10 | 99.61% |
Feb '10 | 99.98% |
Mar '10 | 99.93% |
Apr '10 | 99.95% |
May '10 | 100% |
Jun '10 | 100% |
Jul '10 | 99.99% |
Aug '10 | 99.81% |
Sep '10 | 99.91% |
Oct '10 | 99.99% |
Nov '10 | 99.98% |
Dec '10 | 99.97% |
Percentage of time that a request for a websignon UserLookup request is returned within 5 seconds from within our datacenter* (target: 99.5%)
Month | % |
---|---|
Jan '10 | 99.99% |
Feb '10 | 100% |
Mar '10 | 99.97% |
Apr '10 | 99.6% |
May '10 | 100% |
Jun '10 | 99.99% |
Jul '10 | 99.99% |
Aug '10 | 100% |
Sep '10 | 100% |
Oct '10 | 100% |
Nov '10 | 100% |
Dec '10 | 100% |
* This might seem contrived. But 5 seconds is the threshold at which other applications will time-out a request to websignon, and since the vast majority of WSOS-enabled apps live in our datacentres, that's where we should measure from.