miniblog.

← Back to all posts
Jun 25, 2019 at 23:57
Playing with perf today! It's really interesting to see low-level details of where compute time is going. Branch prediction works well most of the time! (At least for this workload.) Based on https://jvns.ca/blog/2014/05/13/profiling-with-perf/ and
Photo
I can spy on my CPU cycles with perf!
I can spy on my CPU cycles with perf!
Profiling in rust application
Profiling in rust application
As always in performance analysis, the answer depends on what exactly you want to know (for example, exact "number of calls to a function" is a very expensive quantity to measure, so most profilers prefer to give you an approximate "percent of time spent in the function" instead). But in my opinion, the best "default choice" these days is a hardware-assisted sampling profiler. These tools are either operating system or hardware-specific, here are some references that you can look up: Linux: p...
X / ?

Related Posts

Feb 5, 2026 at 09:59
3
Test code is total: we require it to always terminate or it's a failure! It also typically has 100% line and branch coverage. I feel way less nervous about refactoring tests, you can always just run them.
May 24, 2023 at 05:19
I'm writing an experimental PL and I want to exercise it on real programs asap. These need to be useful (so I actually try them), but simple (my PL is unfinished). My current ideas: * A git fuzzy branch switcher (shell commands) * dotfiles sync (filesystem access) Suggestions?
Aug 23, 2019 at 23:21
Merge any sequence of patches (e.g. rebasing a branch) feels like it relies on hope. Whether or not you get conflicts, whether or not the output is syntactically valid or does the right thing: sometimes the computer does too little, and other times it does too much.