NgRx Store vs. StoreDevtools: Evaluating Runtime‑Check Disabling for Low‑Traffic Apps

Integration‑Boundary: Store & StoreDevtools

When a production Angular application has a very small state and receives minimal traffic, developers often consider turning off NgRx runtime checks (e.g., runtimeChecks: false in StoreModule.forRoot) to reduce bundle size and memory overhead. However, the NgRx DevTools extension remains bundled unless explicitly omitted, and it still relies on change‑detection hooks that can inflate memory usage even when runtime checks are disabled.

The core question is whether the small performance gains from disabling runtime checks justify the continued inclusion of DevTools in such a low‑traffic environment, or if the DevTools module should be removed altogether to maximize efficiency.

Key uncertainties include the exact memory footprint of DevTools when runtime checks are off, the impact on startup latency, and the trade‑off between debugging convenience and resource consumption.

Questions:

• How much additional memory does the DevTools module consume when runtime checks are disabled?
• Does omitting DevTools noticeably reduce first‑load latency in a low‑traffic application?
• What is the cost‑benefit of retaining DevTools for debugging versus the performance savings of removing it?