When a tier cannot afford even a paced traversal, how do you produce a per-prefix memory breakdown off the serving path?

## Why you would leave the serving path at all A paced traversal is usually enough. You leave it behind for one of three reasons: the tier has no spare capacity even for a slow walk; you cannot reach the host and the operator interface offers something better than a client-side walk; or the walk needs to be repeated regularly and you would rather it never touched production. ## Three routes 1. **A following copy of the tier.** Point the paced walk at a node that follows the primary and answers no reads. The measurement's cost lands on a machine nobody is waiting on. Two caveats: the node runs slightly behind, and if it is quietly serving reads it is not off the serving path at all. 2. **A point-in-time whole copy.** If the deployment already writes one on a schedule, walking it on another machine costs the serving tier nothing extra. If it does not, you are asking for one to be taken, which is a real charge against the tier. 3. **An export from an operator interface.** On a managed instance you may have no host access and no file. What the operator interface offers — an export, a key inventory, a downloadable copy — may be the only route that does not run through the serving process. ## What taking a copy actually costs - **The copy-on-write pause.** Taking a whole copy of a large in-memory dataset can stall serving briefly while the copy is established, and the process can hold noticeably more memory for as long as the copy is being written, because pages changed during the write exist twice. On a tier already near its ceiling, that is precisely the wrong moment. - **Where you take it from.** Take it from a node that serves no traffic where the shape allows. Taking it from the primary at peak is the version of this answer that gets someone paged. - **Whether it exists at all.** Some stores in this class produce no on-disk copy whatsoever, and many deployments disable it deliberately because the tier holds only replaceable data. Assuming a copy is lying around is assuming one product's configuration. ## What the breakdown loses | Loss | Why it happens | What to do about it | |---|---|---| | Staleness | The copy is as of its timestamp | Compare the age against the growth rate you already measured | | Bytes are not memory | On-disk form is serialized, not resident | Report relative shape — which prefixes dominate — not exact bytes | | One node only | Each node holds its own entries | Take and merge one copy per node, and keep the node in the report | | Data leaves the box | The copy contains production values | Treat it as production data wherever it is analysed | The second row is the one most often got wrong. A copy on disk tells you reliably that one prefix is ten times another; it does not tell you how many bytes of the memory ceiling either occupies, because the representation in memory and the representation in the copy are different things. If the question is "who should shrink", relative shape is enough. If the question is "how much headroom do we get back", it is not, and you need a figure from the running store. ## Handling the data A volatile tier frequently holds sessions, claims, tokens and personal data. A copy of it is a copy of all of that. Walking it on a workstation moves production data onto a workstation, and an analysis run "just to find the big prefixes" is not an exemption. Do the walk somewhere the data is already allowed to be, keep only the rollup, and destroy the copy afterwards. If the only thing you actually need is key names and sizes, prefer a route that never materialises values. ## Choosing between routes 1. Is there a node that serves no traffic? Run the paced walk there — it is live, it is exact, and it costs nothing you care about. 2. Is a whole copy already being written on a schedule? Walk that, and accept relative shape. 3. No host access? See what the operator interface will export, and otherwise fall back to the paced walk from a client, which needs only a connection. 4. None of the above, or the tier holds nothing on disk by design? The paced walk is the answer, slowed down until it is affordable, or the callers instrument themselves.