News for hackers. Stuff that matters.
Re:Coz: Causal Profiling by j-pb on Sunday April 21, 2024 @04:47AM (#40104124)
You are ignoring that even single threaded code has a lot of sources of concurrency and side-effects; memory/caches, branch prediction, prefetching...

Watch the talk and look at the examples. Most of them are single-threaded; a bad hash-function causing bucket collisions and linear inserts; SQLite using an indirection table, killing speculative execution and code prefetching.

Those two wouldn't really show up in a sampling profiler, because they still take up a tiny amount of time.

Sampling profilers show you where time is spend, Causal profilers show you what performance side effects every line of code has.

Re:Coz: Causal Profiling by IshKebab on Sunday April 21, 2024 @07:38AM (#40104873)
I have literally discovered and fixed the "bad hash function" case at work using gperftools. I'll watch the talk again anyway.