Pipelines take a lot longer to run (because the load test environments are expensive we have one or two and serialize test runs on them to stop test runs stepping on each other, but the teardowns are slow, especially on failed runs)
To keep the test run fast we limit them to about 5 minutes but this creates unrealistic expectations of how fast our code would actually need to scale.
But it is nice knowing which changes have broken the load test. Hunting them down is so painful.
What I’d to have is proper metrics showing how close we are to our Non Functional Requirements over time to make it easier to sell “Performance stories” ahead of breaking the NFR rather than just fixing it as we break.
I’m not sure what’s happened to Pinboard I hope Maciej is alright.
I tweeted him ages ago asking about if the pin a URL page could become responsive so I don’t have to use a separate mobile app. He’s responded with a joke. Years later and I’m still using the mobile app.