Skip to content

v1.9.0 — @harperfast/prerender-browser

Choose a tag to compare

View all tags
@harper-joseph harper-joseph released this 08 Jul 21:31
v1.9.0
a86be9d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

@harperfast/prerender-browser v1.9.0

Per-render phase timing and per-worker CPU telemetry in the worker stats log, to diagnose render-throughput ceilings (network-wait vs in-browser CPU) and right-size CONCURRENCY.

Added to each per-window worker stats log line

  • phaseMs — mean/p50/p95/max for each render phase:
    • navTtfb — main-document TTFB (origin/edge response time; isolates a slow/pinned upstream IP)
    • navTotal — full page.goto incl. waitUntil
    • settle — post-nav scroll / network-idle / DOM-stable loop
    • postProcess — final in-page serialize/flatten
  • cpu — respects the N-workers-per-container topology:
    • workerCores / nodeCores / browserCores — this worker only (Node process + its own Chrome process tree via /proc, incl. reaped-child CPU)
    • container — whole-pod cgroup usage + utilization, reported separately (shared by all workers, not per-worker)
    • avgConcurrent (Little's law) + coresPerRender — for concurrency tuning (CPU-bound concurrency ≈ limitCores / coresPerRender)

Notes

  • Sampled once per stats window — no per-render overhead.
  • Degrades to null on hosts without procfs/cgroup.
  • No config or API surface changes; drop-in.

Consumers install the tarball asset attached to this release:
https://github.com/HarperFast/prerender-plugin/releases/download/v1.9.0/harperfast-prerender-browser-1.9.0.tgz

Assets 4
Loading