Stamping typeset PDFs cuts a 180,000-copy watermark run from 90 CPU-hours to 2

Print layout is the expensive half of PDF generation, the post argues, and a stamp skips it ^[10]. Pagination is a global problem ^[11]. A font substitution on page 3 can push a heading onto page 4. Every later break then shifts, the page count changes, and so does a "Page 7 of 214" footer that is itself laid-out content ^[11]. Engines resolve this with multiple passes and a fixed-point check. When the passes do not converge, they pick something and move on ^[12]. Stamping draws on pages that already exist, so none of that work runs again ^[10].

A browser pipeline that regenerates from markup pays the pagination cost on every output file, so its bill grows with recipients instead of documents ^[15]. The post's 90 CPU-hours also come before the memory ceiling that forces teams to cap headless-browser concurrency well below core count ^[3][9].

The 45-to-1 figure rests on two placeholder constants and one assumption: that the masters are already typeset ^[4]. "The ratio is what you should carry away, not my placeholder constants," the author wrote ^[7]. Readers are also told to measure p50 render time on their own page templates before going near a capacity plan ^[8]. I would add a test for the assumption. If all 30,000 masters needed a fresh layout each month at 1.8 s, that is 54,000 CPU-seconds, or 15 CPU-hours ^[2]. The stamping path would then total about 17 CPU-hours against 90, roughly 5 to 1. With six recipients per document, the ratio stays under 6 however cheap the stamp gets ^[3].

Retention turns on determinism. ISO 32000-2 files carry a creation timestamp, a file identifier and generated font subset tags, so two runs over identical input give different bytes unless those are pinned ^[13]. For a team whose compliance position is that it can regenerate the exact artifact, the post says "byte-level determinism is not a nice-to-have, it is the entire claim." ^[14] A stamped copy takes its page breaks from the master, so a font substitution cannot move them at stamping time ^[5]. The metadata still has to be pinned ^[13]. The available text of the post ends before it says which artifacts a stamping pipeline lets a team stop keeping.

Without byte-identical regeneration, the copies themselves are what a team has to keep ^[14]. The post calls retention the only cost term that grows without anyone deciding to grow it ^[18]. "Nobody reviews that line item," the author wrote ^[17].