Skip to content
English - United States
  • There are no suggestions because the search field is empty.

Understanding DPU Consumption (Data Processing Unit)

This article breaks down what affects your DPU consumption and how to monitor it.

BEEM uses Data Processing Units (DPUs) to measure how much computational work is being done across your workspace. Whether you’re running data pipelines, refreshing datasets, or setting up secure connections, DPUs help track usage across the platform in a consistent and transparent way.

What Counts Toward DPU Usage?

DPU consumption is tied to any active processing on the platform. Here are the most common actions that will consume DPUs:

  • Pipelines: Every time a pipeline is triggered (manually or on a schedule), DPUs are used to process and move data.

  • Ingestion Jobs: Loading data into BEEM from external sources (APIs, files, databases) consumes DPUs.

  • Dataset Refreshes: Refreshing a dataset to pull in new or updated data will use DPUs.

  • Flows: Any transformation or computation flow that processes data within BEEM will draw from your DPU balance.

If you’re actively working with data, chances are you’re using DPUs.


Infrastructure and Add-on Services That Impact Usage

Beyond data jobs, certain infrastructure or connection features can also increase your DPU consumption:

  • VPN Connections: If your workspace uses a VPN to connect to on-premise data sources, maintaining and using that tunnel will add to your usage.

  • Data Migration Services (DMS): Managed services such as automated migration scanning or change detection may also consume DPUs.

  • Bastion Hosts: These act as secure entry points to protected networks, and their use during data access operations can contribute to consumption.

  • Data Gateway: If your data is behind a firewall or on-prem, and you’re using a gateway to enable access, processing through this layer can also consume DPUs.

These tools enhance connectivity and security but come with associated usage costs depending on how often they’re used.


Subscription Plans: Pay-As-You-Go vs. Included DPUs

Your plan determines how DPU usage translates into billing:

  • Pay-As-You-Go: You’re charged based on the number of DPUs consumed. This model offers flexibility for workspaces with variable usage.

  • Monthly Included DPUs: Some plans include a fixed amount of DPU credits per month. You’ll only incur overage charges if you exceed the included amount.

If you’re unsure which plan you’re on, you can check your Billing & Usage settings or reach out to support.


How to Monitor Your DPU Consumption

To keep track of your usage:

  • Open the BEEM app.

  • Look in the lower left corner of the sidebar.

  • You’ll see your current DPU usage (refreshed daily), along with your plan’s limit if applicable.

This gives you an at-a-glance view of how much you’ve used and helps you avoid unexpected overages.


Tips for Managing DPU Consumption

  • Schedule Jobs Strategically: Avoid overly frequent refreshes or pipeline runs unless necessary.

  • Batch Data Loads: Group multiple smaller ingestions into a single job where possible.

  • Review Flows and Dependencies: Ensure that downstream refreshes aren’t triggered unnecessarily.

  • Audit VPN and Gateway Use: If you’re using secure connections, assess whether they’re being used efficiently.


If you still have questions about your usage or want help optimizing your workflows, feel free to contact our support team.