Sign inTry Free

Usage and Forecasting

On this page

Overview

A single, centralized page to view your SingleStore Helios usage including Credit consumption, Storage usage, and Data Transfer – where Credits are being consumed, how usage fluctuates over time, and projected future consumption.

Use this page to:

  • Track Compute, Storage, and Transfer usage over time

  • See remaining contracted Credits and how they're projected to be consumed by forecasting future usage based on historical trends

  • Simulate the impact of configuration changes — such as resizing, suspending, or deploying resources — before you make the changes

  • Download and export Usage reports

Note

Forecasts and simulations are estimates based on historical usage patterns and the assumptions configured by the user. Actual billed usage may vary.

View Usage Over Time

Usage is shown as a time series that you can view across several durations:

Duration

What it shows

Current month

Daily Usage so far this month, plus a forecast through the end of the month

Last 3 months + next 1 month

Historical usage plus a forecast for remainder of current month plus the next month

Last 6 months + next 3 months

Historical usage plus a forecast for remainder of current month plus the next three months

Monthly

Historical usage for discrete calendar months, no forecast

Last Year

Historical usage for trailing 12 months, no forecast

All Time

Full historical usage, no forecast

Forecasts are calculated using algorithmic regression over the selected historical window. For the current day, the time series also projects a forecast through the end of the day based on usage so far.

Usage Bar and Remaining Contracted Credits

For any selected time period, the Credit usage bar summarizes:

  • Used — Contracted: Pre-purchased Credits already consumed

  • Forecasted — Contracted: Pre-purchased Credits projected to be consumed

  • Used — On-Demand: On-demand Credits already consumed

  • Forecasted — On-Demand: On-demand Credits projected to be consumed

A monthly breakdown table shows, for each month in the selected range:

  • Remaining balance of pre-purchased, contracted Credits

  • Actual and forecasted pre-purchased, contracted Credits consumption

  • Actual and forecasted On-demand Credits consumption

Note

Remaining contracted credit calculations currently reflect Active commits and subscriptions. Contracts in an Upcoming state are not yet factored in, which can affect projected on-demand usage near a contract renewal boundary.

Usage Breakdowns

Usage views can be broken down and filtered by:

  • Resource Name

  • Resource Type – e.g. Cluster, Notebook, Python UDF

  • Cloud – AWS, Azure, or GCP

  • Region – e.g. N Virginia

Simulate Future Usage

The Simulate Changes tool lets you model how changes to your deployment configurations would impact future credit consumption and spend, without having to build your own spreadsheet-based forecast. Components that can be changed in a Simulation include:

  • Resizing

  • Cache Configuration

  • Compute Scale

  • Single or Multi Availability Zone

Last modified:

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In