Skip to main content

Utilization dashboard

how-to · Reviewed 2026-07-31 · FEAT-0021 GA

The Utilization Dashboard is the capacity counterpart to the Economics Dashboard. Where the Economics view reports what a month cost, this one reports what was consumed: core hours, storage, data transfer, and which members accounted for them.

Like the Economics Dashboard, it covers a single month at a time, selected from the picker in the title bar.

Core Utilization in its Continuous view, above Hardware Usage by Coretype and Top Storage Usage by Member.

What each widget shows​

Core Utilization charts the compute core hours the workspace or organization consumed across the month, and it carries the more useful of the dashboard's two toggles. By Day totals core hours for each day, which is the view you want when the question is how much was consumed. Continuous instead plots active cores over time, which is the view that shows you how concentrated that consumption was. The two answer different questions: a month with one enormous overnight run and a month of steady daytime work can total the same core hours while looking nothing alike under Continuous.

Hardware Usage by Coretype breaks the same consumption down by the coretypes it ran on, and toggles between Usage and Charges. The two orderings are often different, because an expensive coretype can dominate your spend on fairly modest usage while a cheap one dominates your hours. If you are deciding what to commit to, read the Usage view. If you are explaining a bill, read Charges.

Top Storage Usage by Member and Top Transfer Usage by Member each list the five members accounting for the most storage and the most data movement respectively, with the workspace named alongside each member so the figures are attributable at organization level.

Software Charges reports per-application charges for the month, and is the same data the Economics Dashboard shows.

Storage is reported as a monthly average​

The storage figure here is the monthly average per user in a given workspace. It is neither the total at month end nor the peak during the month.

That distinction matters whenever you are reconciling a figure against what someone tells you they are storing. A member who uploaded 2 TB on the last day of the month shows a small average, because the data was only present for a day. A member who held 500 GB for the whole month shows a larger one. Both numbers are correct, and only the second reflects a persistent cost.

For a current snapshot rather than a monthly average, use the Storage column in the jobs list.

What the dashboard is useful for​

Top Storage Usage by Member is the fastest route to reducing storage cost. Storage bills continuously rather than per job, and in most workspaces a handful of members account for the bulk of it, so this widget tells you who to talk to. See archive and delete jobs for what to do next.

Hardware Usage by Coretype tells you whether your actual coretype mix matches what you have committed to. If most of your consumption sits on a coretype outside your commitment plan, you are paying On-Demand Priority rates on the bulk of your work while a commitment goes underused.

Core Utilization is the check that matters most under On-Demand Reserved and Bring-Your-Own-Compute arrangements. There is no real-time charge in your currency to track in those cases, so core hours against a core-hour budget are the only meaningful measure of consumption you have.

What the dashboard will not do​

The dashboard reports one month at a time and does not support a date range, so there is no annual view and no way to compare two months side by side within it. For any trend across months, export from billing and reports instead.

Core Utilization draws on the same source data as the Billing CSV and refreshes on the same schedule. The page itself fetches in real time, so each load shows the latest source data available, but a job that finished in the last few minutes may not be counted yet.