[nine_k]

Fast code is easy. But slow code is equally easy, unless you keep an eye, and measure.

And measuring is hard. This us why consistently fast code is hard.

In any case, adding some crude performance testing into your CI/CD suite, and signaling a problem if a test ran for much longer than it used to, is very helpful at quickly detecting bad performance regressions.

[mattigames]

Exactly, another instance where perfect can be the enemy of good, many times you are better out deploying something to prod, have some fairly good logging system and whenever you see an spike in slowness you try to replicate the conditions that made it slow, and debug from there, instead of expecting to have the impossible perfect measuring system that can detect even missing atoms of networking cables.

[auc]

Agreed, not worth making a huge effort toward an advanced system for measuring an ATS until you’ve really built out at scale