News for hackers. Stuff that matters.
Re:The logging framework isn't a bottleneck, and other lies ... by kasey_junk on Wednesday May 13, 2020 @10:10PM (#23174433)
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 for these uses.

Re:The logging framework isn't a bottleneck, and other lies ... by gav on Wednesday May 13, 2020 @10:47PM (#23174717)
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.

Re:The logging framework isn't a bottleneck, and other lies ... by ColanR on Wednesday May 13, 2020 @11:37PM (#23174988)
> 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.

Re:The logging framework isn't a bottleneck, and other lies ... by cowsandmilk on Wednesday May 13, 2020 @10:37PM (#23174641)
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.
Re:The logging framework isn't a bottleneck, and other lies ... by _bxg1 on Thursday May 14, 2020 @04:12PM (#23184757)
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.