BigRedEye

8 ms·

1.
by BigRedEye 2mo ago
I think this single fact is a major source of enshittification in large software products, especially in the era of ML/AI. If your quality is 99%, it sounds like "you have solved your task", but in reality there is a long tai
2.
by BigRedEye 6mo ago
At Perforator, we also started from Google's beautiful pprof, but then eliminated all nested repeated fields, converging to https://github.com/yandex/perforator/blob/main/perforator/pr... . Repe
3.
by BigRedEye 6mo ago
I believe this is a case of convergent invention – the idea of pushing DWARF/.eh_frame unwinding into eBPF seems to have occurred to several people around the same time. For example, there's a working implementation discussed as e
4.
by BigRedEye 2y ago
At Yandex we have a similar profiler that supports native languages seamlessly, with addition to Python/Java: https://github.com/yandex/perforator . It's exciting to see new profilers from big players!
5.
by BigRedEye 2y ago
Great question! Perforator indeed looks similar to Pyroscope. However, we think that the closest existing solutions are https://parca.dev , closed-source Google Wide Profiling, and, speaking of the agent, the beautiful OpenTeleme
6.
by BigRedEye 2y ago
It depends on the event that was sampled to generate the profiles. For example, if you sample instructions by collecting a stack trace every N instructions, you won't actually see foo() burning the CPU. However, if you look at CPU cycl
7.
Show HN: Perforator – cluster-wide profiling tool for large data centers(github.com)
78 points by BigRedEye 2y ago|13 comments
8.
by BigRedEye 2y ago
A short discussion can be found here: https://news.ycombinator.com/item?id=42888185
9.
by BigRedEye 2y ago
Yes, existing limitations apply. Without hardware LBR support, we cannot provide sPGO profiles. However, the basic profiling should work fine.
10.
by BigRedEye 2y ago
Yes. Although we are studying CSSPO, which uses a mixed (LBR + software-sampled stacks) approach.
11.
by BigRedEye 2y ago
22 minutes for a medium-sized repo is probably slow enough to optimize.
12.
Intel Publishes “x86-S” Specification for 64-Bit Only Architecture(phoronix.com)
24 points by BigRedEye 3y ago|2 comments