How to measure database read cost without a tool that costs you reads

What should be true before you start?

Before you trust a cost tool, ask how it measures. If it runs EXPLAIN on your queries, scans a profiler collection, or polls your database to build its dashboard, it is spending reads to tell you about reads. The only honest design observes the result your application already received and counts that.

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.

• Ask whether the tool runs any query of its own to measure.
• Prefer counting the result already returned over profiling the database.
• Check that the dashboard reads a summary, not your raw data.

How do you find where the reads go?

Observe-only means the meter sits on the result your query already produced — the row count, the documents returned — and increments an in-memory tally. About once a minute it writes a single small summary. Nothing it does issues a read against your database, so watching cost never adds to it.

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 a meter that counts results already returned, not one that profiles.
• Confirm it adds no query — no EXPLAIN, no profiler scan, no polling.
• Let it keep counts in memory and flush one small summary periodically.
• Point the dashboard at that summary so it never scans your data.
• Verify your reads did not rise after installing the tool.

import { installPgMeter, bucket } from "@cross-deck/buckets"
import { Client } from "pg"

// counts the rows this SELECT already returned — runs no query of its own
installPgMeter({ Client })

await bucket("report", () => pool.query("SELECT ..."))

Where do teams get this wrong?

The irony to avoid is a cost tool that becomes a line item — measuring reads by adding reads.

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.

• Tools that run EXPLAIN or profiler queries on production to measure.
• Dashboards that scan your collections every time you open them.
• Polling loops that re-read data just to keep a cost chart fresh.

How does Crossdeck Buckets surface this?

Crossdeck Buckets is observe-only by design: it counts the rows and documents your queries already returned, keeps the tally in memory, flushes one small summary about once a minute, and the dashboard reads only that summary. The thing measuring your reads never adds one.

So you can trust the number without paying for it. The cost of knowing your read cost is zero reads — and that is the only way a cost tool earns a place on a production read path.

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