3 ms·
you know what would be interesting... is if there was some kind of equivalent for dtrace or strace or gdb.. but instead of collecting statistics on performance
by donbright 8y ago
you know what would be interesting... is if there was some kind of equivalent for dtrace or strace or gdb.. but instead of collecting statistics on performance or call trees of functions, it could instead tell you statistics on who wrote the code that your machine is running, line by line.
- haihaibye 8y agoCould modify debug symbols to contain git blame output then collect it in a profiler. We'd probably just learn who wrote the busy/wait kernel loop.
- dankohn1 8y agoThis is by project instead of by machine, but CNCF develops DevStats to show a number of statistics on each of our projects, including the companies behind the development. https://k8s.devstats.cncf.io/d/9/companies-table?orgId=1 https://k8s.devstats.cncf.io/d/9/companies-table?orgId=1 Disclosure: I am executive director of CNCF.