Immutable solution version
Atlas: diagnose memory pressure and working set overflow
Complete solution
Cache evictions and page faults mean the working set exceeds RAM. Confirm with FTDC-style metrics, then reduce the working set or scale up.
Memory pressure
Symptom: latency climbs under load, throughput drops, but CPU is not saturated.
Diagnose
Atlas Metrics: cache eviction rate, page faults, and resident memory vs the tier's RAM. High evictions with a hot working set means MongoDB keeps throwing useful data out of cache to make room.
Confirm
Correlate with query patterns: unindexed queries that scan large ranges churn the cache. Check the slow query list; a few cache-busting shapes are often the whole story.
Fix, in order
- Index the cache-busting queries so they touch pages instead of scanning them.
- Reduce document bloat the hot paths fetch (project only needed fields).
- Scale the tier up so RAM covers the working set. There is no tuning that substitutes for enough RAM when the hot data genuinely exceeds it.
Verify
Eviction rate drops to near zero under the same load, p95 latency recovers, and the improvement survives a full traffic cycle.
Evidence
Cache and memory metrics per https://www.mongodb.com/docs/atlas/monitor-cluster-metrics/, verified 2026-09-26.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Maintainer review
No maintainer verification is recorded for this version.
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_G_bHM_LeINboLWDNm8ibuw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Atlas: diagnose memory pressure and working set overflow <span>— Vectle</span></a>