3 ms·
Even in context it is hard to understand this: "The performance wins that these can provide far outweigh the comparatively tiny loss in performance." My guess
by amne 3y ago
Even in context it is hard to understand this: "The performance wins that these can provide far outweigh the comparatively tiny loss in performance."
My guess is that on average the potential performance discovered with the techniques this enables is higher than the guaranteed negligible performance loss.
- saagarjha 3y agoYes, that's correct.
- o11c 3y agoThat is highly optimistic though. Profiling is hard even when you know what you're doing, and doing it wrong can easily lead to pessimization (thinking particularly about if your profiling workload exercises a different set of branches).
- brancz 3y agoHyperscalers have long been doing infrastructure-wide profiling (or "Google-Wide Profiling" as the first whitepaper on the topic calls it [1]). This tech allows Google to reduce infra-resource usage by multiple percentage points per quarter. [1] https://research.google/pubs/google-wide-profiling-a-continuous-profiling-infrastructure-for-data-centers/ https://research.google/pubs/google-wide-profiling-a-continu...
- o11c 3y ago"Software that runs at scale" is a very different story than "Software that is shipped with a distro", unfortunately. Very few distro packages can even define what a normal workload looks like.
- dralley 3y agoThat's precisely why it's nice for users to be able to collect these profiles themselves.