Documentation
¶
Overview ¶
Command perfreport measures exex against a sample binary and prints a Markdown table: the parse/startup cost, every `-o` view's render time and allocation volume, each interactive (TUI) view's full-frame render cost, and the process's peak resident memory.
It exercises the real code paths (binfile.Open, dump.View/DisasmTo, ui.New), so the numbers track what a user actually pays. CI feeds it the freshly built exex binary (self-disassembly: always present, a realistic ~10 MB native object), and appends the table to the workflow step summary so regressions show up per push.
Usage: perfreport [-runs N] <sample-binary>
Click to show internal directories.
Click to hide internal directories.