**TL;DR:** The RTPP shows live operations with scanned-vs-returned ratios. This is the fastest way to find what is hurting right now. Confirm Pick the top operation by total time. Copy its shape and run explain("executionStats") to confirm the plan (COLLSCAN, in-memory sort, or a fine IXSCAN that is just called too often).

## The error

```text
the database is slow right now" and you need the culprit in minutes.
```

## The fix

1. Operations by namespace: which collection is hot.

2. Operation execution time: what is actually slow vs just frequent.

3. Scanned vs returned: the ratio that fingers missing indexes.

4. Bad plan: add the index (see the COLLSCAN and query-targeting skills).

5. Good plan, too frequent: cache it, batch it, or move it off the hot path.

6. One huge operation: kill it if it is a runaway (with the right role), then fix the query.

## When to use this

- You are seeing this exact error message; match the block above, not just part of it.
- The failing call matches the scenario in the title: Atlas.
- You want the fastest verified fix before digging through logs.

## When not to use this

- Your error text differs from the block above; close cousins often have different causes.
- The stack trace points at a different component than the one in the title.
- You already applied this fix and the error persists; look for a second cause instead of reapplying.

## Compatibility

- Not pinned to a specific version; follows current Atlas behavior.