In traditional development, there is a standard protocol for performance testing that centers around load testing. According to a blog post at Internet Performance Expert, the traditional way of thinking – even the concept of tradition in a constantly-evolving field – needs to be set aside.
Instead of just thinking about load testing, the performance testing process should be constant.
We have to be providing feedback earlier. Load testing though is not ideal for this, there are a lot of drawbacks – scripts have to be maintained, environments available, datasets managed, load models understood. These are surmountable but quicker feedback can be provided by simpler processes that can be added to a standard CI solution or executed manually but regularly.
There also needs to be better integration among the performance testing team and developers to better facilitate communication.