Several factors can impact application performance:
We recommend that you use bare metal Compute instances because instance bandwidth scales with the number of oCPU's. Bare metal Compute instances provide the greatest bandwidth. Virtual machines (VMs) are bandwidth limited based on the number of CPUs consumed. Single oCPU VM Compute instances provide the least bandwidth.
Subnets can be either AD-specific or regional. The type of subnet you choose to create your File Storage resources in can affect latency. You can create File Storage resources in either type of subnet.
Regional subnets allow Compute instances to connect to any mount target in the subnet regardless of AD, with no additional routing configuration. However, to minimize latency, place mount targets in the same AD as Compute instances just as you would in an AD-specific subnet.
For more information, see VCNs and Subnets.Tip
If you want to verify that your instance and mount target are in the same availability domain, you can view the availability domain for any mount target in its Details page, in the Mount Target Information tab:
A file system is always in the same subnet as its associated mount target.
You can also view the availability domain for any instance in its Details page, in the Instance Information tab:
By not providing explicit values for mount options such as rsize and wsize, the client and server can negotiate the window size for read and write operations that provide the best performance.