Perftiquette #8

Perftiquette episode 8


KISS – keep it simple, stupid.
You’ve just learned how to automate your test execution, you’ve automated your washing machine, your coffee machine turns on once you enter the kitchen and a tiny robot asks you what its purpose is. Now it’s time for your performance tests, right?

Once you’ve harnessed the power of optimizing algorithms, data structures and architecture, it is very tempting to optimize your test scripts, or bring new levels of abstractions to simplify the test execution.

The problem is, the time spent on optimizing your tests is not spent on optimizing your application and in most cases it’s easier and more cost-efficient to add an additional load generator to your test pool than to fight for a few bytes of memory or a few CPU cycles to do some off-action processing.

There are of course cases of bad test designs, where users are stuck in some redundant and extremely tight progressing loops and this should be addressed before you reach for additional test resources. Guess what – your performance engineering practices apply there as well: address the problem at hand, don’t over complicate it and improve iteratively. Premature optimization is the worst enemy of code performance.

hashtag#performancetesting hashtag#performanceengineering hashtag#testdesign hashtag#kiss