Consumption Usage | VantageCloud Lake - Review Consumption Usage - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-02-17
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

The Consumption page in VantageCloud Lake Console provides visibility into an organization's compute and storage utilization. As organization admin, you use it to see how your organization consumes compute and storage resources.

To review consumption usage, select on the navigation panel.

Unit consumption on the Compute tab has the monthly consumption breakdown for the environment, organizations, compute groups, and so on. The date and time of the last refresh is at the top of the page.

You can refine the interval, such as hourly, daily, weekly, and so on. For example, you can view hourly intervals to ensure that compute clusters are available during high-demand periods and inactive during low-demand periods. Weekly and monthly intervals help you assess overall usage and manage costs based on use.

On the Compute tab, you can do the following:
  • Select an environment name in the Total table to view consumption by the organizations and compute groups in that environment.
  • Select the download icon to download a spreadsheet with the consumption data.
  • Select Incremental to view units consumed in a given time period.
  • Select Cumulative to view total units consumed. This the month-by-month total units.
  • Select a chart label to hide or show consumption for that item, such as primary cluster or organization.
On the Storage tab, you can do the following:
  • View storage consumption of Block Storage and Object File System.
  • Select on or all environments to view in the graph.
  • Select a chart label to hide or show consumption for that item.
  • Select the download icon to download a spreadsheet with the storage data.
    Amounts shown for object storage are monthly averages.

VantageCloud Lake uses a consumption-based model using unit as the compute measurement metric. Units are consumed when VantageCloud Lake compute resources are active and available to perform workloads. You can control when compute resources are running, allowing for cost flexibility.

The primary cluster consumption per hour is calculated by the instance size multiplied by the instance count. The following table shows units consumed by size for the primary cluster and the compute clusters:
Cluster Lake Lake+
Primary cluster Available instance sizes vary by service provider.
  • XSmall = 2 units
  • Small = 4 units
  • Medium = 7 units
  • Large = 10 units
  • XLarge = 13 units
  • 2XLarge =20 units
  • 3XLarge = 27 units
Available instance sizes vary by service provider.
  • XSmall = 2.4 units
  • Small = 4.8 units
  • Medium = 8.4 units
  • Large = 12 units
  • XLarge = 15.6 units
  • 2XLarge = 24 units
  • 3XLarge = 32.4 units
Compute Cluster
  • XSmall (1 node) = 10 units
  • Small (2 nodes) = 20 units
  • Medium (4 nodes) = 40 units
  • Large (8 nodes) = 80 units
  • XLarge (16 nodes) = 160 units
  • 2XLarge (32 nodes) = 320 units
  • XSmall (1 node) = 12 units
  • Small (2 nodes) = 24 units
  • Medium (4 nodes) = 48 units
  • Large (8 nodes) = 96 units
  • XLarge (16 nodes) = 192 units
  • 2XLarge (32 nodes) = 384 units

To increase or decrease performance on both the primary cluster and compute clusters, contact your representative to initiate a service ticket. Changes to clusters occur during upgrades. Instance size and count impact the unit consumption rate on the primary cluster. Cluster size changes to compute clusters also impact the unit consumption rate.

Storage is measured and charged in terabytes. The Storage tab provides visibility to the committed storage size of block storage, and the actual provisioned usage of block storage and object storage. Block storage is for data related to time-sensitive workloads or short service-level agreement requests, and is accessible to the primary cluster. Object storage is for data that supports less time-sensitive analytics, long-running queries, and tables in extract, transform, and load (ETL) processes. Object storage is accessible to compute clusters.
Backup storage is separate and not included in your consumption data. Native Object Storage (NOS) is also not included.