October 2011
Intermediate to advanced
400 pages
9h 23m
English
So you’re writing the next big thing, or at least trying to. Is it Google+ or Facebook? You’ve got a limited budget, and you have to be ready for 100 to 100,000,000 hits tomorrow!
You did your best during development to write efficient code, and it all seems fairly speedy. One-second load times? That’s good enough, right? Except now you have actual users, not just your small dev team hitting your server, and things are starting to fall over … oh, no!
There are two ways to know if your code needs performance help: by benchmarking during development, or when your servers start to topple from the load. Benchmarking, as it relates to web applications, typically means “stress testing”—throwing as ...