Basic performance guidance for FSx File Gateway - Amazon Storage Gateway
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon S3 File Gateway documentation has been moved to What is Amazon S3 File Gateway?

Volume Gateway documentation has been moved to What is Volume Gateway?

Tape Gateway documentation has been moved to What is Tape Gateway?

Basic performance guidance for FSx File Gateway

In this section, you can find guidance for provisioning hardware for your FSx File Gateway VM. The instance configurations that are listed in the table are examples, and are provided for reference.

For best performance, the cache disk size must be tuned to the size of the active working set. Using multiple local disks for the cache increases write performance by parallelizing access to data and leads to higher IOPS.

Note

We don't recommend using ephemeral storage. For information about using ephemeral storage, see Using ephemeral storage with EC2 gateways.

In the following tables, cache hit read operations are reads from the file data that is served from cache. Cache miss read operations are reads from the file data that is served from Amazon FSx for Windows File Server.

The following table shows an example FSx File Gateway configuration.

FSx File Gateway performance on Windows clients

Example Configuration Protocol Write throughput (file sizes 1 GB) Cache hit read throughput Cache miss read throughput

Root disk: 80 GB, io1 SSD, 4,000 IOPS

Cache disks: 2 x 2 TiB NVME

Minimum network performance: 10 Gbps

CPU: 32 vCPU | RAM: 244 GB

SMBv3 - 1 thread 162 MiB/sec (1.4 Gbps) 403 MiB/sec (3.4 Gbps) 288 MiB/sec (2.4 Gbps)
SMBv3 - 8 threads 511 MiB/sec (4.3 Gbps) 571 MiB/sec (4.8 Gbps) 567 MiB/sec (4.8 Gbps)
Note

Your performance might vary based on your host platform configuration and network bandwidth. Write throughput performance decreases with file size, with the highest achievable throughput for small files (less than 32MiB) being 16 files per second.