3583153 - SAP Datasphere Capacity Unit Consumption

 Understanding Capacity Unit Billing: How Memory Size Influences Hourly Costs in Datasphere

SAP Datasphere

1. Access Datasphere tenant
2. System -> Configuration
3. Tenant Configuration
4.  The right-hand side displays the Capacity Units consumed in the current month, alongside those expended in the preceding month.

The consumption of Capacity Units per hour is contingent upon various factors, including the size of the memory.

Detailed information regarding pricing can be found within this document.

Additionally, the Pricing Calculator provides an estimation of monthly usage.

Take an example at today's data in internal system:

You have consumed 3,485.08 CUs this month:
785.25 CUs used by Foundation Blocks
50.12 CUs used by Storage
2,444.16 CUs used by Memory
205.56 CUs used by Data Lake Storage

To calculate it, let's take the "CUs used by Memory", as example, as you can see in the document, each 64 GB memory consumes 2.28 CU per Hour. In this tenant, it is 256GB memory in configuration, which consumes 9.12 CU per hour as per the documentation.

Up to day (March 12):

1. Total hours of operation:

   • From March 1, 00:00 to March 11, 24:00 → 264 hours
   • From March 12, 00:00 to current time (assumed 12:00) → 12 hours
   • Total: 276 hours

2. Accounting for data update delay (6 hours):

   • Effective hours: 270 hours

3. Total CU consumption:

   • 270 hours × 9.12 CU/hour = 2462.4 CU
   • Rounded down, this amounts to 2462 CU --> Similar as 2444.16 CUs

KBA , DS-BM , Datasphere Billing Metrics , Bug Filed