Skip to content

prumo v0.2.0

Latest

Choose a tag to compare

@github-actions github-actions released this 10 Nov 18:56
· 18 commits to main since this release
91efe53

This release adds two things prumo measures. One is where a run's time goes, from engine start to the closed PDF. The other is what the usual speed-ups would save on your document.

  • Phases. prumo time now opens with the run cut into startup, preamble, begin-document, typesetting, shipout, end-document and finalization. prumo times the engine process itself, so the seven add up to the wall time you waited for. compare has the same table across engines and ranks them by wall time.
  • Environments. --env times the environments you name. The default is tikzpicture, axis, tcolorbox, tblr, longtable, tabularx, minted, lstlisting and forest.
  • prumo whatif. It rebuilds your document with one change at a time and times it against the plain build: the preamble precompiled with mylatexformat, draft mode, and tikz's external library (experimental, and only with --shell-escape). Every build runs on a copy, warm-up first, then the baseline and the variants in turns. A saving inside the spread of the runs is reported as noise, the probe's estimate of the most a change can save sits beside it, and a variant whose pages, words or rendering changed says so. A variant that fails is a row with its first error, not a crash.
  • Records without a build. prumo time output.prumo reads the record file of a build prumo did not run, such as Overleaf's. docs/overleaf.md says how.
  • Benchmarks. Ten documents on three engines, from a one-line file to the 7,710-page Stacks Project, with what the probe costs (7 ms on the one-line file, under 6% everywhere) and what each whatif experiment saves. Charts and tables are in docs/benchmarks.
  • A failed build prints its first ! error. doctor checks for mylatexformat, and doctor --check-log tells a file opened only to test that it exists from one read outside the hooks.

The probe is v0.2: it adds records for the end of \begin{document}, the last page and the environments you watch. The PDF is still byte-identical with and without it, on all three engines. The JSON stays at schema 1. Fields were added and none renamed.

Other ways in: cargo install prumo, a binary below (Linux x86-64 and arm64 static, macOS Intel and Apple silicon, Windows x86-64, each with a sha256 next to it), or Docker: ghcr.io/kevinraymond/prumo:0.2.0 carries a full TeX Live and :0.2.0-small carries scheme-small, both for amd64 and arm64. Run prumo doctor first.