Which technique does NOT help you get the optimal performance out of the Oracle Cloud Infrastructure (OC1) File Storage service?

Question

Options

• ASerialize operations to the file system to access consecutive blocks as much as possible.
• BLimit access to the same Availability Domain (AD) as the File Storage service where possible.
• CRight size compute instances from where file system is accessed based on their network capacity.
• DStore files across multiple directories in the file system.
• EIncrease concurrency by using multiple threads, multiple clients, and multiple mount targets.

• A
  73% (11)
• B
  7% (1)
• C
  7% (1)
• D
  13% (2)

Explanation

Oracle Cloud Infrastructure File Storage is a fully managed file storage service that can be accessed concurrently by thousands of compute instances. To optimize the performance of File Storage, consider the following guidelines: - While it is possible to access mount targets from any availability domain in a region, for optimal performance, place File Storage resources in the same availability domain as the Compute instances that - File Storage performance increases with parallelism. Increase concurrency by using multiple threads, multiple clients, and multiple mount targets. In particular, scalability will be greatest when clients and threads are accessing independent portions of the file system - Use tools to run file operations in parallel. The File Storage engineering team has developed parallel tar and untar (puntar), parallel copy (parcp), and parallel remove (parrm) tools. These tools are available in the fss-parallel-tools package in Oracle Linux. - The available bandwidth to a file system can significantly impact its performance. In Oracle Cloud Infrastructure, larger instances (more CPUs) are entitled to more network bandwidth. File Storage performance is best with Oracle bare metal instances or large VM shapes - To minimize latency, clients, mount targets, and file systems should be in the same availability domain. - For best performance, don't set any mount options such as rsize or wsize when mounting the file system. In the absence of these options, the system automatically negotiates optimal window sizes. - Due to the limitations of Oracle Cloud Infrastructure's VNICs, each mount target is limited to about 600 MB/s of read or write traffic. If you have bandwidth-heavy workloads, consider spreading your workload across multiple mount targets after your file system exceeds 10 TB.

No community discussion yet for this question.