Webdev:Velocity 2009 Notes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
* Metrics that Matter | *Metrics that Matter | ||
** Measure end user response time, not network or server time | **Measure end user response time, not network or server time | ||
** Measure flows (registration, checkout, etc) | **Measure flows (registration, checkout, etc) | ||
* Fixing Twitter | *Fixing Twitter | ||
** Make everything a queue | **Make everything a queue | ||
** Use google analytics for outage page to track problems | **Use google analytics for outage page to track problems | ||
* Shopzilla | *Shopzilla | ||
** Increased performance has a direct correlation with higher revenue and pageviews. | **Increased performance has a direct correlation with higher revenue and pageviews. | ||
** Averages don't mean anything, get the median and percentiles. | **Averages don't mean anything, get the median and percentiles. | ||
* Overall | *Overall | ||
** Measure everything you can | **Measure everything you can | ||
** IT & Webdev/engineering should overlap and have same goals | **IT & Webdev/engineering should overlap and have same goals | ||
Revision as of 17:50, 7 July 2009
- Metrics that Matter
- Measure end user response time, not network or server time
- Measure flows (registration, checkout, etc)
- Fixing Twitter
- Make everything a queue
- Use google analytics for outage page to track problems
- Shopzilla
- Increased performance has a direct correlation with higher revenue and pageviews.
- Averages don't mean anything, get the median and percentiles.
- Overall
- Measure everything you can
- IT & Webdev/engineering should overlap and have same goals