4 ms·
Well, The easy, general lesson is you need optimize "in the large" from day one, meaning having architecture that won't bottle necks but avoid optimization "in
by joe_the_user 15y ago
Well,
The easy, general lesson is you need optimize "in the large" from day one, meaning having architecture that won't bottle necks but avoid optimization "in the small", because the small can be changed easily.
On the other hand, I'd say that the test suite you use for optimization should be taken as much from your real world experiences or expectations as possible. It would be different from a suite of unit tests or even integration tests.
- ebiester 15y agoI'd suggest that your happy path integration tests would be a good place to start, coupled with a database loaded more heavily than you expect in the real world.