4 ms·

For performance centric uses you tend to run benchmarks and performance tests a lot. Having production quality hardware for the dev cycle is extremely valuable

• cowsandmilk 7y ago
  Sure, but my IDE doesn’t have be running there. Code compiles and is benchmarked on prod hardware (and OS environment), I write code on machine designed for my productivity.
• gav 7y ago
  Performance testing is hugely valuable but nothing beats having performance metrics captured and made available from production. You never really know how things are going to perform until you see them under real load against real data. There’s been many times I’ve been bitten by this, including the one time we found that a small portion of users would set the number of results returned to the max and scroll through hundreds of pages of results, blowing the cache for everyone. I tend to hear “we run performance tests so we don’t get regressions” a lot more than “we monitor the performance of releases to canaries and rollback”. It shouldn’t be one or the other, both are invaluable.
  • ColanR 7y ago
    > small portion of users would set the number of results returned to the max and scroll through hundreds of pages of results Yup, that sounds like me. I do exactly that whenever the pages are slow to load. Rather wait longer, once.
• _bxg1 6y ago
  I'm not saying remove it from the dev cycle; you can stand up a remote server for whatever testing happens during your normal workflow without a) buying a physical server box to use as your workstation, or b) constraining yourself to working via a terminal.