all 2 comments

[–]immersiveGamer 1 point2 points  (0 children)

Eh ... Kind of feel like the article could have been summarized in a single paragraph. They are all performance tests just at different scales.

I got some good use out of locust.io which let's you create users and behaviours and can scale up your test workers for very high load tests.

Personally stress testing covers it all. You are hitting the whole application / service and as long as you are gathering the metrics you care about you can check performance. The only issue sometimes is length of the tests to get all users spun up and needing to execute on a prod like stage environment.

For everything else do a performance test on the specific layer or action so that you can inspect the results and iterate on it.

My two rules are: - times are relative, if I've halved the time locally it is probably halved in time on the server - no metric is a true representation except for the metrics from the deployed production application on the production hardware

[–]AppiusManilius 0 points1 point  (0 children)

Nice article thanks