How to find which feature is driving your MongoDB read load

What should be true before you start?

Know what Atlas charges for: the cluster tier and compute you provision, not a per-read fee. That means the lever is read load — the documents your queries return. Cut the load and you can run a smaller cluster; the read meter exists to show you where that load comes from.

Read cost is a measurement problem before it is an optimization problem. You cannot cut what you cannot attribute, and a database bill is a single total with no memory of which feature, screen, or background job spent it. The first job is to make the reads legible — grouped by the part of the product that caused them — so the expensive path is obvious instead of theoretical.

• Accept that Atlas billing is cluster-based, so documents read is load, not a bill.
• List the collections and queries you suspect of returning the most documents.
• Name the buckets you want documents-read grouped under.

How do you find where the reads go?

The MongoDB meter patches the driver's result-returning reads once — find().toArray(), aggregate().toArray(), and findOne() — and counts the documents each returns, attributed to the active bucket. It reads what the query already produced, so it runs no explain() and no profiler scan.

The honest version of this measures the work already in hand. A good read meter counts the documents or rows a query already returned — it never runs an extra query, an EXPLAIN, or a profiler scan to measure, because a cost tool that itself costs reads is worse than none. Counting stays in memory, and attribution rides on the name you gave the path.

• Install the meter by passing the driver classes from your mongodb import.
• Wrap a suspect path in bucket("home-feed", ...).
• Let every find, aggregate, and findOne report the documents it returned.
• Rank features by documents read; the heaviest is your target.
• Narrow that query or add an index, then confirm the bucket falls.

import { installMongoMeter, bucket } from "@cross-deck/buckets"
import { FindCursor, AggregationCursor, Collection } from "mongodb"

installMongoMeter({ FindCursor, AggregationCursor, Collection })

await bucket("home-feed", () =>
  db.collection("posts").find({ live: true }).toArray())

Where do teams get this wrong?

The mistake is chasing a per-read price that Atlas does not charge, instead of cutting the document load that decides your cluster size.

Most read-cost surprises are not one greedy query; they are an unattributed one. A scheduled job that re-reads a collection every few minutes, a dashboard that re-scans on every refresh, or a listener that fans out on each change can outspend every user-facing feature combined — and none of it shows up until you group the reads by cause and one bar dwarfs the rest.

• Looking for a per-read dollar figure that Atlas does not bill.
• Running explain() across production to find a query you have not located yet.
• Letting an aggregate pipeline return thousands of documents the screen never shows.

How does Crossdeck Buckets surface this?

Crossdeck Buckets measures documents read by feature — the raw load behind your Atlas cluster — without ever running a profiling query. It names MongoDB and Atlas as the deployment it covers and keeps the measurement observe-only.

So you stop guessing at cluster size and start reading the cause: this aggregate, on the server, returns the most documents — narrow it, and the load that sized your cluster comes down.

This is also the upgrade path, and it stays free across the step. The open-source collector shows the reads on one surface, grouped by the buckets you named — no account needed. Sign up to Crossdeck and a single SDK install adds the dimension the collector alone cannot see: which environment each read ran in — your server, your web app, your dashboard, or a mobile build — folded into the same buckets, still free. A spike stops being a guess between “is it the backend or the client?” and becomes a labelled segment you can read at a glance.

What should a healthy setup let you do?

After instrumenting, you should be able to open one view and name the top three features by read load, point to the single path driving the biggest bar, and say which environment it ran in. If that still takes a spreadsheet and a guess, the setup is not finished.

A healthy setup also makes the next change cheap to verify. Shipping an index, a cache, or a narrower query should move a specific bucket down — and you should be able to see that it did, not infer it from next month’s invoice.

• Rank features by read load and find the biggest single path.
• See which environment a read ran in — server, web, dashboard, or mobile.
• Confirm a fix moved the right bucket down, not just the bill as a whole.

What should you review after it is running?

Review the biggest bucket first — the single largest source of reads is almost always where the cheapest win lives. Then look for the rhythm that does not match your users: a steady overnight wave with nobody on the app is a machine, not a customer, and machines are the easiest reads to cut.

Treat the read meter as an operating surface, not a one-time audit. Each spike, each new feature, and each background job is a chance to confirm the cost is attributed before it compounds.

• Start at the largest bucket; that is where the cheapest win usually is.
• Watch for read patterns with no matching user activity.
• Re-check attribution whenever you add a feature or a scheduled job.

How should the whole team use it?

Read cost is not only an engineering concern. A founder watching runway wants the trend and the biggest line item. An engineer wants the exact path and environment to fix. Both are reading the same buckets, just at different depths.

When the cost is attributed by feature and labelled by environment, the conversation changes from “the database bill went up” to “this job, on the server, doubled — here is the fix.” That is the difference between a vague worry and a one-line task.

• Founder: watch the trend and the largest cost driver.
• Engineering: jump to the exact path and environment to fix.
• Everyone: reason from one attributed view instead of a single total.

Frequently asked questions