Cloud Storage FUSE automatically applies optimized default configuration values when
it runs on high-performance Compute Engine machine types, such as the A3, A4,
and TPU v6e series. These defaults help you get high throughput for demanding
workloads without manual tuning. Any values that you set manually at mount time
take precedence.

## Machine types

Configuration values are automated for the following high-performance
Compute Engine machine types:

| Series type | Machine type |
|---|---|
| [A2 machine series](https://docs.cloud.google.com/compute/docs/gpus.md.txt#a100-gpus) | `a2-megagpu-16g` `a2-ultragpu-8g` |
| [A3 machine series](https://docs.cloud.google.com/compute/docs/gpus.md.txt#a3-series) | `a3-edgegpu-8g` `a3-highgpu-8g` `a3-megagpu-8g` `a3-ultragpu-8g` |
| [A4 machine series](https://docs.cloud.google.com/compute/docs/gpus.md.txt#b200-gpus) | `a4-highgpu-8g-lowmem` |
| [A4X machine series](https://docs.cloud.google.com/compute/docs/gpus.md.txt#gb200-gpus) | `a4x-highgpu-4g` |
| [A4X Max machine series](https://docs.cloud.google.com/compute/docs/gpus.md.txt#gb300-gpus) | `a4x-maxgpu-4g-metal` |
| [TPU v5e](https://docs.cloud.google.com/tpu/docs/v5e.md.txt) | `ct5l-hightpu-8t` `ct5lp-hightpu-8t` |
| [TPU v5p](https://docs.cloud.google.com/tpu/docs/v5p.md.txt) | `ct5p-hightpu-4t` `ct5p-hightpu-4t-tpu` |
| [TPU v6e (Trillium)](https://docs.cloud.google.com/tpu/docs/v6e.md.txt) | `ct6e-standard-4t` `ct6e-standard-4t-tpu` `ct6e-standard-8t` `ct6e-standard-8t-tpu` |
| [TPU 7x (Ironwood)](https://docs.cloud.google.com/tpu/docs/tpu7x.md.txt) |   |
|   | `tpu7x-standard-4t` |

## Automated configuration values

When a supported machine type is detected, Cloud Storage FUSE automatically applies
the following configuration values:

| Cloud Storage FUSE configuration file field | Cloud Storage FUSE CLI option | Automated configuration value |
|---|---|---|
| `metadata-cache:negative-ttl-secs` | `--metadata-cache-negative-ttl-secs` | `0` |
| `metadata-cache:ttl-secs`^1^ | `--metadata-cache-ttl-secs`^1^ | `-1` |
| `metadata-cache:stat-cache-max-size-mb` | `--stat-cache-max-size-mb` | `1024` |
| `implicit-dirs` | `--implicit-dirs` | `true` |
| `file-system:rename-dir-limit` | `--rename-dir-limit` | `200000` |
| `write:global-max-blocks` | `--write-global-max-blocks` | `1600` |

^1^Setting this configuration to `-1` significantly boosts
performance by always serving files from the cache. Be aware that this
configuration bypasses consistency checks, which can lead to serving
outdated data. For details on managing data consistency, refer to
[Overview of caching in Cloud Storage FUSE](https://docs.cloud.google.com/storage/docs/cloud-storage-fuse/caching.md.txt).

## Further performance tuning

When you use a high-performance Google Cloud machine type, the
configuration values detailed on this page are automatically applied. However, you
can further fine-tune your machine for optimal performance using the
following methods:

- Use the [Performance tuning best practices guide](https://docs.cloud.google.com/storage/docs/cloud-storage-fuse/performance.md.txt) to improve Cloud Storage FUSE
  using key Cloud Storage FUSE features and configurations to achieve maximum
  throughput and optimal performance.

- If you're running training, serving, or checkpointing and Just in Time (JIT)
  cache workloads on Google Kubernetes Engine clusters that use Cloud GPUs or Cloud TPU
  to access large datasets in Cloud Storage, you can streamline your setup
  by utilizing pre-configured YAML files to mount your Cloud Storage buckets
  directly into your pods more efficiently. For more information and
  instructions on how to use pre-configured GKE YAML files, see
  [Use pre-configured GKE YAML files to optimize Cloud Storage FUSE performance](https://docs.cloud.google.com/storage/docs/cloud-storage-fuse/performance.md.txt).

- If you're running training, serving, or checkpointing workloads using
  Cloud Storage FUSE, you can use the [`profile` field](https://docs.cloud.google.com/storage/docs/cloud-storage-fuse/config-file.md.txt#profile) or
  [`--profile` command option](https://docs.cloud.google.com/storage/docs/cloud-storage-fuse/cli-options.md.txt#profile)
  to automatically adjust specific Cloud Storage FUSE configurations for optimal
  performance based on the specific workload type. For more information, see
  [Profile-based configurations for AI/ML workloads](https://docs.cloud.google.com/storage/docs/cloud-storage-fuse/profile-based-configurations.md.txt).

## What's next

- Learn how to [tune Cloud Storage FUSE for optimal performance](https://docs.cloud.google.com/storage/docs/cloud-storage-fuse/performance.md.txt).

- Use a [pre-configured GKE YAML file](https://docs.cloud.google.com/storage/docs/cloud-storage-fuse/sample-yaml-files.md.txt) to configure tuning best practices.