JavaScript Memory Footprint on Low-Traffic Node.js Workloads

JavaScript Runtime Overhead

The goal is to minimize operational costs for a JavaScript workload characterized by very low request volume.

Runtime Constraints

The primary constraint is that the inherent overhead of a runtime environment persists even when traffic is minimal.

What is the typical steady-state memory consumption of a minimal Node.js server implementation?

Does the garbage collection frequency significantly impact the baseline memory usage under infrequent event loop activity?