How to prove a database cost fix actually worked, before and after

What should be true before you start?

A monthly bill is a bad instrument for proving a fix: it mixes your change with traffic growth, other features, and time. To know whether a specific change worked, you need to watch the specific thing you changed — the one bucket — across the moment you shipped it.

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.

• Pick the single bucket your fix is meant to reduce.
• Mark the exact moment you ship so before and after are clean.
• Judge the fix on that bucket's reads, not the whole bill.

How do you find where the reads go?

The before-and-after view splits a bucket's reads at the moment you mark a fix. Reads per hour before, reads per hour after — same feature, same query, just on either side of your change. That isolates your fix from everything else happening in the app.

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.

• Confirm the bucket you intend to reduce is being measured.
• Ship your change — an index, a cache, a narrower query.
• Mark the fix so the timeline splits at that moment.
• Compare reads per hour before and after on that bucket.
• If it did not fall, the fix missed — iterate before moving on.

import { bucket } from "@cross-deck/buckets"

// keep the bucket name stable across the fix so before/after compare cleanly
await bucket("dashboard", () => loadDashboard(userId))

Where do teams get this wrong?

The mistake is judging a single fix by the whole bill, where growth and other features drown out the signal.

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.

• Attributing a bill change to your fix when traffic moved at the same time.
• Changing the bucket name during the fix, so before and after no longer compare.
• Declaring success without confirming the targeted bucket actually fell.

How does Crossdeck Buckets surface this?

Crossdeck Buckets stamps the moment you mark a fix and splits the bucket's reads-per-hour at that point, so the before and after belong to the same feature and isolate your change — and it shows the environment, so you know the saving landed where you expected.

Cost work becomes a closed loop: change one path, mark it, watch its bucket fall within the hour. If it does not move, you learn immediately — not at the end of the month.

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