Rob Pike's rules are still as relevant as ever, also for web dev: Rule 1. You can't tell where a program is going to spend its time. Bottlenecks occur in surpr

Rob Pike's rules are still as relevant as ever, also for web dev: Rule 1. You can't tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don't try to second guess and put in a speed hack until you've proven that's where the bottleneck is. Rule 2. Measure. Don't tune for speed until you've measured, and even then don't unless one part of the code overwhelms the rest. http://users.ece.utexas.edu/~adnan/pike.html http://users.ece.utexas.edu/~adnan/pike.html