HVM_domU

Xen HVM domU 4.11.amazon testing on Amazon Linux 2 via the Phoronix Test Suite.

Compare your own system(s) to this result file with the Phoronix Test Suite by running the command: phoronix-test-suite benchmark 2406071-NE-HVMDOMU1168
Jump To Table - Results

Statistics

Remove Outliers Before Calculating Averages

Graph Settings

Prefer Vertical Bar Graphs

Multi-Way Comparison

Condense Multi-Option Tests Into Single Result Graphs

Table

Show Detailed System Result Table

Run Management

Result
Identifier
View Logs
Performance Per
Dollar
Date
Run
  Test
  Duration
HVM_domU
June 07
  57 Minutes
Only show results matching title/arguments (delimit multiple options with a comma):
Do not show results matching title/arguments (delimit multiple options with a comma):


HVM_domUOpenBenchmarking.orgPhoronix Test Suite2 x Intel Xeon E5-2686 v4 @ 3.00GHz (32 Cores / 64 Threads)Xen HVM domU (4.11.amazon BIOS)Intel 440FX 82441FX PMC16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 16384 MB + 8192 MB RAM8 x 1900GB Amazon EC2 NVMe Instance StorageCirrus Logic GD 5446Amazon ElasticAmazon Linux 25.10.217-205.860.amzn2.x86_64 (x86_64)GCC 7.3.1 20180712xfsXen HVM domU 4.11.amazonProcessorMotherboardChipsetMemoryDiskGraphicsNetworkOSKernelCompilerFile-SystemSystem LayerHVM_domU BenchmarksSystem Logs- Transparent Huge Pages: madvise- --build=x86_64-redhat-linux --disable-libunwind-exceptions --enable-__cxa_atexit --enable-bootstrap --enable-checking=release --enable-gnu-indirect-function --enable-gnu-unique-object --enable-initfini-array --enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --enable-libatomic --enable-libcilkrts --enable-libitm --enable-libmpx --enable-libquadmath --enable-libsanitizer --enable-multilib --enable-plugin --enable-shared --enable-threads=posix --mandir=/usr/share/man --with-arch_32=x86-64 --with-gcc-major-version-only --with-isl --with-linker-hash-style=gnu --with-tune=generic - Scaling Governor: intel_cpufreq performance - CPU Microcode: 0xb000040- gather_data_sampling: Not affected + itlb_multihit: KVM: Mitigation of VMX unsupported + l1tf: Mitigation of PTE Inversion + mds: Vulnerable: Clear buffers attempted no microcode; SMT Host state unknown + meltdown: Mitigation of PTI + mmio_stale_data: Vulnerable: Clear buffers attempted no microcode; SMT Host state unknown + reg_file_data_sampling: Not affected + retbleed: Not affected + spec_rstack_overflow: Not affected + spec_store_bypass: Vulnerable + spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization + spectre_v2: Mitigation of Retpolines STIBP: disabled RSB filling PBRSB-eIBRS: Not affected + srbds: Not affected + tsx_async_abort: Vulnerable: Clear buffers attempted no microcode; SMT Host state unknown

HVM_domUbyte: Dhrystone 2sysbench: RAM / Memorysysbench: CPUstream: Copystream: Scalestream: Triadstream: Addintel-mlc: Idle Latencyintel-mlc: Max Bandwidth - All Readsintel-mlc: Max Bandwidth - 3:1 Reads-Writesintel-mlc: Max Bandwidth - 2:1 Reads-Writesintel-mlc: Max Bandwidth - 1:1 Reads-Writesintel-mlc: Max Bandwidth - Stream-Triad Likeintel-mlc: Peak Injection Bandwidth - All Readsintel-mlc: Peak Injection Bandwidth - 3:1 Reads-Writesintel-mlc: Peak Injection Bandwidth - 2:1 Reads-Writesintel-mlc: Peak Injection Bandwidth - 1:1 Reads-Writesintel-mlc: Peak Injection Bandwidth - Stream-Triad LikeHVM_domU24673692.35218.7542849.8796686.974685.285280.285084.592.5124285.38116575.42114332.03104939.95114630.28124019.0116317.6114083.2104642.8109757.0OpenBenchmarking.org

BYTE Unix Benchmark

This is a test of BYTE. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgLPS, More Is BetterBYTE Unix Benchmark 3.6Computational Test: Dhrystone 2HVM_domU5M10M15M20M25MSE +/- 201566.24, N = 324673692.3

Sysbench

This is a benchmark of Sysbench with the built-in CPU and memory sub-tests. Sysbench is a scriptable multi-threaded benchmark tool based on LuaJIT. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgMiB/sec, More Is BetterSysbench 1.0.20Test: RAM / MemoryHVM_domU11002200330044005500SE +/- 17.35, N = 35218.751. (CC) gcc options: -pthread -O2 -funroll-loops -rdynamic -ldl -laio -lm

OpenBenchmarking.orgEvents Per Second, More Is BetterSysbench 1.0.20Test: CPUHVM_domU9K18K27K36K45KSE +/- 2.33, N = 342849.871. (CC) gcc options: -pthread -O2 -funroll-loops -rdynamic -ldl -laio -lm

Stream

This is a benchmark of Stream, the popular system memory (RAM) benchmark. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgMB/s, More Is BetterStream 2013-01-17Type: CopyHVM_domU20K40K60K80K100KSE +/- 126.81, N = 596686.91. (CC) gcc options: -mcmodel=medium -O3 -march=native -fopenmp

OpenBenchmarking.orgMB/s, More Is BetterStream 2013-01-17Type: ScaleHVM_domU16K32K48K64K80KSE +/- 49.72, N = 574685.21. (CC) gcc options: -mcmodel=medium -O3 -march=native -fopenmp

OpenBenchmarking.orgMB/s, More Is BetterStream 2013-01-17Type: TriadHVM_domU20K40K60K80K100KSE +/- 84.30, N = 585280.21. (CC) gcc options: -mcmodel=medium -O3 -march=native -fopenmp

OpenBenchmarking.orgMB/s, More Is BetterStream 2013-01-17Type: AddHVM_domU20K40K60K80K100KSE +/- 70.33, N = 585084.51. (CC) gcc options: -mcmodel=medium -O3 -march=native -fopenmp

Intel Memory Latency Checker

Intel Memory Latency Checker (MLC) is a binary-only system memory bandwidth and latency benchmark. If the download fails you may need to manually download the file from https://www.intel.com/content/www/us/en/developer/articles/tool/intelr-memory-latency-checker.html and place it in your PTS download cache. On some systems root privileges are needed to run the MLC tester. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgns, Fewer Is BetterIntel Memory Latency Checker 3.10Test: Idle LatencyHVM_domU20406080100SE +/- 0.13, N = 392.5

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Max Bandwidth - All ReadsHVM_domU30K60K90K120K150KSE +/- 117.94, N = 3124285.38

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Max Bandwidth - 3:1 Reads-WritesHVM_domU20K40K60K80K100KSE +/- 149.65, N = 3116575.42

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Max Bandwidth - 2:1 Reads-WritesHVM_domU20K40K60K80K100KSE +/- 241.88, N = 3114332.03

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Max Bandwidth - 1:1 Reads-WritesHVM_domU20K40K60K80K100KSE +/- 54.20, N = 3104939.95

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Max Bandwidth - Stream-Triad LikeHVM_domU20K40K60K80K100KSE +/- 12.91, N = 3114630.28

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - All ReadsHVM_domU30K60K90K120K150KSE +/- 392.55, N = 3124019.0

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - 3:1 Reads-WritesHVM_domU20K40K60K80K100KSE +/- 264.21, N = 3116317.6

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - 2:1 Reads-WritesHVM_domU20K40K60K80K100KSE +/- 325.92, N = 3114083.2

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - 1:1 Reads-WritesHVM_domU20K40K60K80K100KSE +/- 270.68, N = 3104642.8

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - Stream-Triad LikeHVM_domU20K40K60K80K100KSE +/- 188.10, N = 3109757.0