blog

Personal blog
git clone git://git.laack.co/blog.git
Log | Files | Refs

commit 0fedd3a60cf8665403dbc99f683dffaca24cf119
parent 825ef17628a4d0c3ceec6482b33ebbffd447fc9e
Author: Andrew Laack <andrew@laack.co>
Date:   Sat, 10 Oct 2026 20:39:01 -0500

incr

Diffstat:
Mposts/wip/basic-software-profiling-cpu-usage.md | 5+----
Aposts/wip/vim-hax.md | 3+++
2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/posts/wip/basic-software-profiling-cpu-usage.md b/posts/wip/basic-software-profiling-cpu-usage.md @@ -1,10 +1,7 @@ TODOS: - since we support http(s) we mustn't hardcode file paths. -- is my statement abt perf_events being collected true? - - like the call graph samples aren't perf_events.... - foreseen results for file w/ python header - # Basic Software Profiling: CPU Usage Collectively, we waste trillions of CPU cycles every day because software isn't profiled frequently. I believe this is an educational problem. @@ -86,7 +83,7 @@ This is the command I ran to generate the data: perf record -g ./ex1 ``` -The `record` command is used to record `perf_events` and other statistics. These are written to the `perf.data` file. By default, `perf record` will sample at 1000Hz while the program is on-CPU. The final option, `-g`, is used to specify we are interested in having the call stack included in our data. +The `record` command is used to run a command and record its performance profile. These are written to the `perf.data` file. By default, `perf record` will sample at 1000Hz while the program is on-CPU. The final option, `-g`, is used to specify we are interested in having the call stack included in our data. To view aggregate information about the data in the `perf.data` file we can run: diff --git a/posts/wip/vim-hax.md b/posts/wip/vim-hax.md @@ -0,0 +1,3 @@ +# Vim Hax + +- persistent undo