Electron Renderer process memory optimization for low-traffic background workloads

Electron's multi-process architecture allocates a separate Chromium instance for every BrowserWindow, which creates a significant memory baseline even for applications with minimal user interaction. For low-traffic workloads, maintaining multiple active renderer processes can lead to unnecessary resource consumption.

While the Main process manages the application lifecycle, the overhead of the Chromium engine in the renderer remains a constraint. There is a design trade-off between maintaining a hidden window to keep the UI state ready and destroying the WebContents entirely to reclaim memory, which then introduces latency during the next user interaction.

Given the default contextIsolation settings in recent versions, what is the most resource-efficient way to handle intermittent background tasks without maintaining a permanent renderer process? Is it more performant to utilize a single hidden window for all background logic or to dynamically create and destroy renderers based on workload demand?