4 ms·
That was discussed at the time on HN: https://news.ycombinator.com/item?id=34632677 https://news.ycombinator.com/item?id=34632677 My comment on that article st
by userbinator 4y ago
That was discussed at the time on HN: https://news.ycombinator.com/item?id=34632677 https://news.ycombinator.com/item?id=34632677
My comment on that article still stands: https://news.ycombinator.com/item?id=34660474 https://news.ycombinator.com/item?id=34660474
tl;dr: don't make code generation worse for everyone else just to appease your one tiny use-case; fix your goddamn tools instead.
- aktau 4y agoWalking the stack via frame pointers is also faster than some other methods (https://blog.felixge.de/reducing-gos-execution-tracer-overhead-with-frame-pointer-unwinding/ https://blog.felixge.de/reducing-gos-execution-tracer-overhe...), it appears. This benefits use cases like profilers and tracers. In big deployments, continuous (sampled) profiling and tracing are common, helping not only with continuous performance improvements in fleets but also helping to root cause outages. Reducing the cost of such infrastructure can pay off.