The sizing is referencing Accelario server, and is also recommended for the Target server(s).
CPU, RAM and Network sizing by data size
Given: | Recommended: | ||||
Shape | Data size | Network | CPU | RAM GB | Instance type for AWS: |
small | up to 500 GB | 1 Gbps | 4 | 8 | Not supported |
medium | 500 GB - 1TB | 1 - 5 Gbps | 8 | 16 | Not supported |
large | 1 - | ||||
5 TB | 5 -10 Gbps | 16 | 32 | c5.4xlarge | |
X large | 5 - 10 TB | 10 - 20 Gbps | 32 | 64 | c5.9xlarge |
XX large | 10 TB and higher | 10 - 40 Gbps | 64 | 128 | c5.18xlarge |
Boundaries of NFS throughput are defined by 2 parameters:
...
Examples of expected NFS throughput (NFS read/write speed) by different settings:
Given: | Expected: | |||
Network | Disk throughput | IOPS | NFS version | NFS throughput (NFS read/write speed) |
1 Gbps | 125 MB/s | 2000 | 3 or higher | 100 - 120 MB/s |
5 Gbps | 600 MB/s | 4000 | 3 or higher | 500 - 600 MB/s |
10 Gbps | 1000 MB/s | 4000 | 4,1 | 800 - 1000 MB/s |
Equation:
| Code Block |
|---|
MIN("DISK THROUGHPUT", "NETWORK BANDWIDTH") - 30 PERCENT
e.g
Netwokr = 10 Gbps = 1.25 GB/s
Disk throughput = 1 GB/s
Then expected NFS throughput will be
min(1.25, 1) = 1 GB/s - 30 percent ~ 800 MB/s,
we can expect sometimes the pick can be up to 1000 MB/s |
...