How does syncing affect a Kaspa node's RAM usage?

During initial sync, a Kaspa node's RAM requirement jumps from its normal ~3 GB up to at least 8 GB. In steady-state operation the node is lightweight — it uses roughly 3 GB of RAM and less than 1% CPU. But syncing from scratch means the node is downloading and processing the full blockDAG history all at once, which is far more memory-intensive. This matters to you as a node operator because starting with less than 8 GB of free RAM risks the sync failing partway through, forcing you to start over.