4 ms·
This is probably the answer. I watched a great talk about this, and how to avoid problems that result from it. The presenter built a framework that made random
by nwallin 6y ago
This is probably the answer.
I watched a great talk about this, and how to avoid problems that result from it. The presenter built a framework that made random changes to alignment of various blocks of code with two different versions of the same microbenchmark until it had high statistical confidence that either one was faster than the other, or it would eject and say that the difference between the two was statistically insignificant. Or something along those lines.
I'm looking for the video now, but I can't find it. Pretty sure it was CppCon but I'm not positive.
- kristjansson 6y agohttps://news.ycombinator.com/item?id=23634519 https://news.ycombinator.com/item?id=23634519 :)
- moonchild 6y agoPossibly 'Performance Matters'? (https://www.youtube.com/watch?v=r-TLSBdHe1A https://www.youtube.com/watch?v=r-TLSBdHe1A)
- dkersten 6y agoThis was the very first thing I thought of when I saw this submission title! Great talk, well worth watching.
- Twirrim 6y agoMy team watched this several months ago now. "Eyeball statistics" he mentions at one stage has been a phrase that has particularly stuck for us from it. So many metrics dashboards etc rely on it to a disturbing degree, if you step back and really think about what it's _actually_ showing you. I almost want to put a warning banner on most of ours. "Beware Eyeball Statistics!"
- nwallin 6y agoThe other one is 99th percentile latency. Lots of people think of 99th percentile latency as the latency that 1% of their users will encounter. But if your site loads 200 assets, almost every site load will hit 99th percentile latency.
- nwallin 6y agoYup! That's the one!