Does pug's built‑in view cache save enough CPU time to warrant its unbounded memory growth in low‑traffic Node apps?
Goal Determine whether enabling Pug's built‑in template cache yields a measurable per‑request latency reduction that justifies allowing the cache to grow without bounds in a low‑traffic Node.js application that may render many distinct templates over time. Constraints and uncertainty The application serves low traffic, so per‑request CPU savings are small, b