V8 8.0: Startup Snapshots for Low‑Traffic Services – Reducing Launch Latency

Goal

Reduce the cost of repeatedly launching a low‑traffic JavaScript service by leveraging V8 8.0’s startup snapshot feature.

Constraints & Uncertainty

The service rarely executes the same functions, yet occasionally loads new modules after the snapshot is taken. The snapshot captures only the heap state at creation time, so any post‑snapshot code must be compiled again, potentially negating startup benefits for long‑running isolates. Additionally, the snapshot size grows with the amount of pre‑initialized data, and the cost of creating the snapshot at build time versus the savings at runtime is unclear.

Specific Questions

• What is the optimal snapshot size for a low‑traffic service that balances startup latency against snapshot creation time?
• Does the presence of a snapshot affect the frequency or duration of minor garbage collections when the service runs infrequently?
• How does the Ignition interpreter’s lack of TurboFan optimization influence CPU usage for functions that are executed only a few times per deployment?