Amazon FSx File Gateway documentation has been moved to What is Amazon FSx 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 S3 File Gateway
In this section, you can find guidance for provisioning hardware for your S3 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.
For Amazon EC2 instances, if you have more than 5 million objects in your S3 bucket and you are using a General Purposes SSD volume, a minimum root EBS volume of 350 GiB is needed for acceptable performance of your gateway during start up. For information about how to increase your volume size, see Modifying an EBS volume using elastic volumes (console).
In the following tables, cache hit read operations are reads from the file shares that are served from cache. Cache miss read operations are reads from the file shares that are served from Amazon S3.
The following tables show example S3 File Gateway configurations.
S3 File Gateway performance on Linux clients
| Example Configurations | 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 disk: 512 GiB cache, io1, 1,500 provisioned IOPS Minimum network performance: 10 Gbps CPU: 16 vCPU | RAM: 32 GB NFS protocol recommended for Linux |
NFSv3 - 1 thread | 110 MiB/sec (0.92 Gbps) | 590 MiB/sec (4.9 Gbps) | 310 MiB/sec (2.6 Gbps) |
| NFSv3 - 8 threads | 160 MiB/sec (1.3 Gbps) | 590 MiB/sec (4.9 Gbps) | 335 MiB/sec (2.8 Gbps) | |
| NFSv4 - 1 thread | 130 MiB/sec (1.1 Gbps) | 590 MiB/sec (4.9 Gbps) | 295 MiB/sec (2.5 Gbps) | |
| NFSv4 - 8 threads | 160 MiB/sec (1.3 Gbps) | 590 MiB/sec (4.9 Gbps) | 335 MiB/sec (2.8 Gbps) | |
| SMBV3 - 1 thread | 115 MiB/sec (1.0 Gbps) | 325 MiB/sec (2.7 Gbps) | 255 MiB/sec (2.1 Gbps) | |
| SMBV3 - 8 threads | 190 MiB/sec (1.6 Gbps) | 590 MiB/sec (4.9 Gbps) | 335 MiB/sec (2.8 Gbps) | |
|
Storage Gateway Hardware Appliance Minimum network performance: 10 Gbps |
NFSv3 - 1 thread | 265 MiB/sec (2.2 Gbps) | 590 MiB/sec (4.9 Gbps) | 310 MiB/sec (2.6 Gbps) |
| NFSv3 - 8 threads | 385 MiB/sec (3.1 Gbps) | 590 MiB/sec (4.9 Gbps) | 335 MiB/sec (2.8 Gbps) | |
| NFSv4 - 1 thread | 310 MiB/sec (2.6 Gbps) | 590 MiB/sec (4.9 Gbps) | 295 MiB/sec (2.5 Gbps) | |
| NFSv4 - 8 threads | 385 MiB/sec (3.1 Gbps) | 590 MiB/sec (4.9 Gbps) | 335 MiB/sec (2.8 Gbps) | |
| SMBV3 - 1 thread | 275 MiB/sec (2.4 Gbps) | 325 MiB/sec (2.7 Gbps) | 255 MiB/sec (2.1 Gbps) | |
| SMBV3 - 8 threads | 455 MiB/sec (3.8 Gbps) | 590 MiB/sec (4.9 Gbps) | 335 MiB/sec (2.8 Gbps) | |
|
Root disk: 80 GB, io1 SSD, 4,000 IOPS Cache disk: 4 x 2 TB NVME cache disks Minimum network performance: 10 Gbps CPU: 32 vCPU | RAM: 244 GB NFS protocol recommended for Linux |
NFSv3 - 1 thread | 300 MiB/sec (2.5 Gbps) | 590 MiB/sec (4.9 Gbps) | 325 MiB/sec (2.7 Gbps) |
| NFSv3 - 8 threads | 585 MiB/sec (4.9 Gbps) | 590 MiB/sec (4.9 Gbps) | 580 MiB/sec (4.8 Gbps) | |
| NFSv4 - 1 thread | 355 MiB/sec (3.0 Gbps) | 590 MiB/sec (4.9 Gbps) | 340 MiB/sec (2.9 Gbps) | |
| NFSv4 - 8 threads | 575 MiB/sec (4.8 Gbps) | 590 MiB/sec (4.9 Gbps) | 575 MiB/sec (4.8 Gbps) | |
| SMBV3 - 1 thread | 230 MiB/sec (1.9 Gbps) | 325 MiB/sec (2.7 Gbps) | 245 MiB/sec (2.0 Gbps) | |
| SMBV3 - 8 threads | 585 MiB/sec (4.9 Gbps) | 590 MiB/sec (4.9 Gbps) | 580 MiB/sec (4.8 Gbps) |
File Gateway performance on Windows clients
| Example Configurations | 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 disk: 512 GiB cache, io1, 1,500 provisioned IOPS Minimum network performance: 10 Gbps CPU: 16 vCPU | RAM: 32 GB SMB protocol recommended for Windows |
SMBV3 - 1 thread | 150 MiB/sec (1.3 Gbps) | 180 MiB/sec (1.5 Gbps) | 20 MiB/sec (0.2 Gbps) |
| SMBV3 - 8 threads | 190 MiB/sec (1.6 Gbps) | 335 MiB/sec (2.8 Gbps) | 195 MiB/sec (1.6 Gbps) | |
| NFSv3 - 1 thread | 95 MiB/sec (0.8 Gbps) | 130 MiB/sec (1.1 Gbps) | 20 MiB/sec (0.2 Gbps) | |
| NFSv3 - 8 threads | 190 MiB/sec (1.6 Gbps) | 330 MiB/sec (2.8 Gbps) | 190 MiB/sec (1.6 Gbps) | |
|
Storage Gateway Hardware Appliance Minimum network performance: 10 Gbps |
SMBV3 - 1 thread | 230 MiB/sec (1.9 Gbps) | 255 MiB/sec (2.1 Gbps) | 20 MiB/sec (0.2 Gbps) |
| SMBV3 - 8 threads | 835 MiB/sec (7.0 Gbps) | 475 MiB/sec (4.0 Gbps) | 195 MiB/sec (1.6 Gbps) | |
| NFSv3 - 1 thread | 135 MiB/sec (1.1 Gbps) | 185 MiB/sec (1.6 Gbps) | 20 MiB/sec (0.2 Gbps) | |
| NFSv3 - 8 threads | 545 MiB/sec (4.6 Gbps) | 470 MiB/sec (4.0 Gbps) | 190 MiB/sec (1.6 Gbps) | |
|
Root disk: 80 GB, io1 SSD, 4,000 IOPS Cache disk: 4 x 2 TB NVME cache disks Minimum network performance: 10 Gbps CPU: 32 vCPU | RAM: 244 GB SMB protocol recommended for Windows |
SMBV3 - 1 thread | 230 MiB/sec (1.9 Gbps) | 265 MiB/sec (2.2 Gbps) | 30 MiB/sec (0.3 Gbps) |
| SMBV3 - 8 threads | 835 MiB/sec (7.0 Gbps) | 780 MiB/sec (6.5 Gbps) | 250 MiB/sec (2.1 Gbps) | |
| NFSv3 - 1 thread | 135 MiB/sec (1.1. Gbps) | 220 MiB/sec (1.8 Gbps) | 30 MiB/sec (0.3 Gbps) | |
| NFSv3 - 8 threads | 545 MiB/sec (4.6 Gbps) | 570 MiB/sec (4.8 Gbps) | 240 MiB/sec (2.0 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.