public sealed class AutoscalingTargets : IMessage<AutoscalingTargets>, IEquatable<AutoscalingTargets>, IDeepCloneable<AutoscalingTargets>, IBufferMessage, IMessage
Reference documentation and code samples for the Google Cloud Bigtable Administration v2 API class AutoscalingTargets.
The Autoscaling targets for a Cluster. These determine the recommended nodes.
The cpu utilization that the Autoscaler should be trying to achieve.
This number is on a scale from 0 (no utilization) to
100 (total utilization), and is limited between 10 and 80, otherwise it
will return INVALID_ARGUMENT error.
public int StorageUtilizationGibPerNode { get; set; }
The storage utilization that the Autoscaler should be trying to achieve.
This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD
cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster,
otherwise it will return INVALID_ARGUMENT error. If this value is set to 0,
it will be treated as if it were set to the default value: 2560 for SSD,
8192 for HDD.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-25 UTC."],[[["The page provides documentation for the `AutoscalingTargets` class within the Google Cloud Bigtable Administration v2 API, specifically for the .NET environment."],["This class is responsible for defining the autoscaling parameters for a Bigtable cluster, which includes setting targets for CPU and storage utilization."],["The latest version available for `AutoscalingTargets` is 3.24.0, but the page also covers versions ranging from 3.23.0 down to 2.4.0."],["The `AutoscalingTargets` class implements multiple interfaces, including `IMessage`, `IEquatable`, and `IDeepCloneable`, enabling it to integrate with Google's protocol buffers system."],["`AutoscalingTargets` properties allow you to configure the target CPU utilization, between 10 and 80 percent, and storage utilization per node, ranging from 2.5TiB to 5TiB for SSD clusters and 8TiB to 16TiB for HDD clusters."]]],[]]
