Small OCI terminology note that I hadn't realized before adding OCI to the dataset: Oracle uses "OCPU" differently than the vCPU language most AWS/GCP/Azure users are used to. In OCI, 1 OCPU generally maps to 1 physical core / 2 hardware threads, so this 8 OCPU Flex VM reports as a 16 vCPU instance in the benchmark data. That makes it closer to the 16 vCPU / 64 GB class when comparing across providers.
Too many benchmark comparisons focus on the best single run. Looking at consistency over time seems to me much more useful than chasing the highest peak performance.
Totally agree. The highest benchmark number is easy to chase. We're more interested in answering a different question: "If I deploy this same VM again next week, what should I expect?" That's the whole reason we keep rerunning the same clusters over time.
Small OCI terminology note that I hadn't realized before adding OCI to the dataset: Oracle uses "OCPU" differently than the vCPU language most AWS/GCP/Azure users are used to. In OCI, 1 OCPU generally maps to 1 physical core / 2 hardware threads, so this 8 OCPU Flex VM reports as a 16 vCPU instance in the benchmark data. That makes it closer to the 16 vCPU / 64 GB class when comparing across providers.
Too many benchmark comparisons focus on the best single run. Looking at consistency over time seems to me much more useful than chasing the highest peak performance.
Totally agree. The highest benchmark number is easy to chase. We're more interested in answering a different question: "If I deploy this same VM again next week, what should I expect?" That's the whole reason we keep rerunning the same clusters over time.