fSync Write Performance

When an application wants to make absolutely sure that changes have been written to disk, it uses the fsync() syscall, which flushes all pending writes to the drive and waits until the data is safely written. This provides important integrity guarantees that are used by databases like MySQL, SQL Server, high-availability filesystems and the etcd service that's the backbone for all Kubernetes clusters.

While modern consumer drives offer hundreds of thousands of IOPS at high queue depths, without any durability guarantees, their fSync performance is very low and varies greatly, which is why we've added this test.

IO Latency

In this section, we take a closer look at the IO latencies of our SSDs, which helps quantify the time it takes for a data transfer to travel through the OS and the SSD controller, get executed, and report its completion back to the application. The numbers presented are the 99th percentile, recording an upper latency limit (=worst case) you can expect from the drive with the given IO load. The 99th percentile was chosen to eliminate outliers caused by random events, like OS processor scheduling, and background processes using up CPU time. Latency is an important factor for enterprise sectors that need to achieve certain quality-of-service levels, but ends up playing an important role to enthusiasts as well. Our goal here is to identify bottlenecks in the controller or flash cell erase process.

Mixed Accesses Patterns

Our final synthetic test workload examines IO performance with various mixed read/write ratios. On the horizontal axis, we start with a 100% read (0% write) operation on the left, moving through various read/write ratios until we reach 100% write (0% read) on the right. The 99% ratio values are especially important data points here, since it's rare to only send read or write operations to a drive. It is much more common to have reads and writes interspaced in between, one source of which is disk "noise" created by the operating system or background programs. The other read/write ratios are useful, because they help determine the performance you can expect from various application scenarios.