False premise of failed transactions

by Perfluencer

Did you know that errors are usually the fastest transactions? Here’s why:

The system stops processing on the stack as soon as a technical or functional error occurs. The failure isn’t free either—it involves rollbacks of already started transactions, rollbacks of the stack, and additional, more verbose logging. However, in general, it’s still faster than a successful transaction.

Mixing the response times of both successful and failed transactions might not be the best option. The higher your error rate, the lower your latency. It’s even worse if your assertions don’t detect these errors, and you report a response time for a non-functioning application.

Now that I think about it, I may have found the origin of the term “non-functional” testing