Figure 5 displays the combined results of the DataStax Enterprise benchmark tests for the read-intensive, write-intensive, and balanced read/write scenarios on the Red Hat OpenShift cluster, while Figure 6 displays the same results for the VMware Tanzu cluster running on NVMe. The x-axis displays the total throughput in operations per second performed during each test’s 10-minute run, while the y-axis displays the mean latency in milliseconds for each operation during the run.

Figure 5. NVMe benchmark results for the DataStax Enterprise read-intensive, balanced read/write, and write-intensive scenarios on the Red Hat OpenShift cluster

The Red Hat OpenShift cluster test consisted of five test runs for each read-intensive, write-intensive, and balanced read/write scenarios. Each data point on the chart represents a test run with a specific number of client threads that simulate client loads. The number of client threads for each test run were:

• First test run: 20 client threads
• Second test run: 80 client threads
• Third test run: 160 client threads
• Fourth test run: 320 client threads
• Fifth test run: 640 client threads

Figure 5 shows that latency moderately increased for the 90 percent read/10 percent write, mixed 50 percent read/50 percent write (balanced read/write), and 10 percent read/90 percent write scenarios as the number of client threads increased. The maximum operations per second occurred with the 90 percent read/10 percent write workload at 201,797 with 640 client threads.

Figure 6. NVMe benchmark results for the DataStax Enterprise read-intensive, balanced read/write, and write-intensive scenarios on the VMware Tanzu cluster

The VMware Tanzu cluster test consisted of six test runs for each read-intensive, write-intensive, and balanced read/write scenarios. Each data point on the chart represents a test run with a specific number of client threads that simulate client loads. The number of client threads for each test run were:

• First test run: 10 client threads
• Second test run: 40 client threads
• Third test run: 80 client threads
• Fourth test run: 160 client threads
• Fifth test run: 320 client threads
• Sixth test run: 640 client threads

Figure 6 shows that latency significantly increased for the 90 percent read/10 percent write scenario at 320 client threads, while latency moderately increased for the mixed 50 percent read/50 percent write (balanced read/write) and 10 percent read/90 percent write scenarios as the number of client threads increased. The maximum operations per second occurred with the 90 percent read/10 percent write workload at 135,815 with 640 client threads.