ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #v8
Learn how to decide between V8's built‑in code cache and a custom snapshot to cut Node.js cold‑start time while staying under a 150 MiB RSS budget.
Learn how V8's Hidden Classes (Shapes) optimize JavaScript property access and why property assignment order can accidentally tank your application's performance.
V8 pointer compression stores 64‑bit object pointers as 32‑bit offsets, halving per‑object memory while keeping full addressability. Learn how it works, its limits, and how to verify it in your embed.
A diagnostic guide to resolving 'JavaScript heap out of memory' errors in V8, covering heap limit adjustments, GC tracing, and leak detection.
The goal is to minimize GC‑induced pause‑time variability for latency‑sensitive Node.js workloads that allocate many short‑lived objects (e.g., Buffers in a tight loop). The constraint is choosing between V8’s incremental (Orinoco) marker, which spreads marking work to lower worst‑case pauses but adds write‑barrier overhead, and the parallel young‑generation
nodejs