# AutoScaling Configurations

Datafy AutoScaler manages your volumes using a set of configurable parameters that control when and how volumes grow and shrink. Datafy's defaults are designed to work well for most workloads, but you can fine-tune behavior per account or per instance through the Configuration page.

For an overview of the grow and shrink lifecycle, see [how-autoscaler-works](https://docs.datafy.io/how-it-works/how-autoscaler-works "mention").

{% hint style="success" %}
Once you activate autoscaling on your volumes they will automatically grow and shrink with the default configurations. Editing these configurations allows behavior fine-tuning and workload specific optimization, it is not needed for storage optimization to work.
{% endhint %}

{% hint style="info" %}
Only users with an **admin** role can edit configurations. Read-only users can view configuration values but cannot make changes.
{% endhint %}

## Configuration Levels

Configurations are set at the **account level** by default, applying to all instances in the account. You can create **instance-level overrides** for specific instances, which take precedence over the account setting. If an instance override is reverted, the value goes back to inheriting from the account level - if the account-level value changes later, the instance will automatically pick up the new value.

## Viewing and Editing Configurations

You can access the [Configurations](https://app.datafy.io/settings/configurations) page by selecting  **Settings → Configurations** in the left sidebar. The navigation tree on the left shows the account and any instances that have configuration overrides. Select an item to view its values on the right.

Each field shows the current value, the default or inherited value below it, and a **Default** or **Revert** indicator showing whether it has been overridden. Click any value to edit it inline - input is validated against the allowed range in real time. Click **Save** to apply your changes. To restore a single field to the default or inherited value indicated below it, click **Revert** next to that field. To restore all fields at once, click **Revert all to default** at the bottom of the page.

To create a new instance-level override, click **Add New Configuration** and select an instance from the searchable list. Instances that already have custom values are labeled **Overridden**. Any fields you don't change will continue to inherit from the account level.

## Configuration Reference

The tables below describe each configurable parameter grouped by the autoscaling operation they affect. For more on how these operations work, see [how-autoscaler-works](https://docs.datafy.io/how-it-works/how-autoscaler-works "mention").

### Autoscaling Activation Configurations

These configurations control the initial autoscaling activation of a volume, how the first managed volume is sized and how the initial data copy is performed.

<table><thead><tr><th width="150.27734375">Name</th><th>Description</th><th width="120.3671875">Default</th><th width="119.89453125">Range</th></tr></thead><tbody><tr><td><strong>Autoscaling Size Factor</strong></td><td>When autoscaling is activated, the initial managed volume size will be at least this factor multiplied by the current used data. A higher value means more free space after activation.</td><td>1.3</td><td>1.1 – 2.0</td></tr><tr><td><strong>Autoscaling Minimum Size (GiB)</strong></td><td><p>The smallest absolute size an autoscaling volume can reach following initial activation. Even if actual usage is lower, the volume will not be sized below this value.</p><p>Volumes with original sizes smaller than this  can not be autoscaled.</p></td><td>50 GiB</td><td>20 – 16,384 GiB</td></tr><tr><td><strong>Autoscaling Minimum Size (%)</strong></td><td>The smallest size an autoscaling volume can reach following initial activation, as a percentage of the original volume size.  Works alongside the absolute minimum, whichever produces a larger size applies.</td><td>10%</td><td>5 – 100%</td></tr><tr><td><strong>Autoscaling Maximum Size (GiB)</strong></td><td>The maximum original volume size eligible for autoscaling. Volumes larger than this will not be autoscaled.</td><td>16,384 GiB</td><td>Up to 16,384 GiB</td></tr></tbody></table>

### Growth Configurations

These control automatic volume growth - when and by how much AutoScaler expands a managed volume as it fills up.

{% hint style="warning" %}
AutoScaler maintains a time based grow triggering mechanism that ensures the volume will never run out of space even when writing to it at the maximum possible rate. The editable configurations below are in addition to this mechanism.
{% endhint %}

<table><thead><tr><th width="149.859375">Name</th><th>Description</th><th width="119.765625">Default</th><th width="120.47265625">Range</th></tr></thead><tbody><tr><td><strong>Grow Factor</strong></td><td>When a grow is triggered, the new volume size will be this factor multiplied by the current size. Higher values add more headroom per grow but temporarily use more storage.</td><td>1.5</td><td>Min 1.1</td></tr><tr><td><strong>Grow Minimum Free Space</strong></td><td>An absolute free-space floor. Growth is triggered when free space on the volume drops below this value. Acts as a safety net to ensure volumes don't run out of space.<br></td><td>5 GiB</td><td>Min 5 GiB</td></tr></tbody></table>

### Shrink Configurations

These control automatic volume shrinking - when and by how much Datafy reduces a volume to reclaim unused capacity and reduce costs.

<table><thead><tr><th width="150.29296875">Name</th><th width="356.76953125">Description</th><th width="120.00390625">Default</th><th width="119.9921875">Range</th></tr></thead><tbody><tr><td><strong>Shrink Threshold (%)</strong></td><td>If not in shrink cooldown (see below), a shrink is triggered when the volume's utilization falls below this percentage (of the volume's current size). For example, at 50%, a volume using only 30 GiB out of a current size of 65 GiB will shrink.</td><td>50%</td><td>0 – 75%</td></tr><tr><td><strong>Shrink Abort Threshold (%)</strong></td><td>If a shrink is already in progress and the expected utilization in the new smaller size rises above this percentage, the shrink is aborted.</td><td>85%</td><td>80 – 100%</td></tr><tr><td><strong>Shrink Size Factor</strong></td><td>When shrinking, the new volume size will be at least this factor multiplied by the current used data, ensuring headroom remains after the operation.</td><td>1.3</td><td>Min 1.1</td></tr><tr><td><strong>Shrink Minimum Size (GiB)</strong></td><td>The smallest absolute size a volume can be shrunk to. Even if actual usage is lower, the volume will not be sized below this value.</td><td>50 GiB</td><td>20 – 16,384 GiB</td></tr><tr><td><strong>Shrink Minimum Size (%)</strong></td><td>The smallest size a volume can be shrunk to, as a percentage of the original volume size. Works alongside the absolute minimum, whichever produces a larger size applies.</td><td>10%</td><td>5 – 100%</td></tr><tr><td><strong>Shrink Cooldown Time</strong></td><td>Minimum wait time after any autoscaling operation (activation, grow, or shrink) before a new shrink can be triggered. Prevents rapid grow/shrink cycling on volumes with fluctuating usage.</td><td>60 min</td><td>Min 1 min</td></tr></tbody></table>