Ask HN: Why aren't you load testing in CI?

When building web services, I've always felt like I should be running load tests in the CI pipeline. Or at least before merging changes. I've seen performance-killing commits get missed until they are in production more than a few times.

But there's always some reason that I never get around to setting it up. The infrastructure takes too long to set up, configuring test execution is too much work, I don't want to block the rest of the build and test process, etc.

I pretty sure I'm not the only one that thinks this is a good idea that they've never gotten around to. What's keeping you from doing load testing in CI? And if you've made the investment, how did you implement it and how is it working for you?