mlc_test

KVM testing on AlibabaCloud 3 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 2306123-NE-2306122NE14
Jump To Table - Results

View

Do Not Show Noisy Results
Do Not Show Results With Incomplete Data
Do Not Show Results With Little Change/Spread
List Notable Results
Show Result Confidence Charts
Allow Limiting Results To Certain Suite(s)

Statistics

Show Overall Harmonic Mean(s)
Show Overall Geometric Mean
Show Wins / Losses Counts (Pie Chart)
Normalize Results
Remove Outliers Before Calculating Averages

Graph Settings

Force Line Graphs Where Applicable
Convert To Scalar Where Applicable
Prefer Vertical Bar Graphs

Multi-Way Comparison

Condense Multi-Option Tests Into Single Result Graphs

Table

Show Detailed System Result Table

Run Management

Highlight
Result
Toggle/Hide
Result
Result
Identifier
Performance Per
Dollar
Date
Run
  Test
  Duration
mlc_test
June 12 2023
  46 Minutes
compare
June 12 2023
  46 Minutes
Invert Behavior (Only Show Selected Data)
  46 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):

mlc_test

Kernel Notes: nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 - Transparent Huge Pages: madvise
Processor Notes: CPU Microcode: 0x1
Security Notes: itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Not affected + retbleed: Not affected + spec_store_bypass: Vulnerable + spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization + spectre_v2: Mitigation of Enhanced IBRS RSB filling PBRSB-eIBRS: SW sequence + srbds: Not affected + tsx_async_abort: Vulnerable: Clear buffers attempted no microcode; SMT Host state unknown

compare

Processor: Intel Xeon Platinum 8475B (4 Cores / 8 Threads), Motherboard: Alibaba Cloud ECS (449e491 BIOS), Chipset: Intel 440FX 82441FX PMC, Memory: 1 x 16 GB RAM, Disk: 43GB Alibaba Cloud Elastic Block Storage, Graphics: Cirrus Logic GD 5446, Network: Red Hat Virtio device

OS: AlibabaCloud 3, Kernel: 5.10.134-13.1.al8.x86_64 (x86_64), Compiler: GCC 10.2.1 20200825, File-System: ext4, Screen Resolution: 1024x768, System Layer: KVM

mlc_testOpenBenchmarking.orgPhoronix Test SuiteIntel Xeon Platinum 8475B (4 Cores / 8 Threads)Alibaba Cloud ECS (449e491 BIOS)Intel 440FX 82441FX PMC1 x 16 GB RAM43GB Alibaba Cloud Elastic Block StorageCirrus Logic GD 5446Red Hat Virtio deviceAlibabaCloud 35.10.134-13.1.al8.x86_64 (x86_64)GCC 10.2.1 20200825ext41024x768KVMProcessorMotherboardChipsetMemoryDiskGraphicsNetworkOSKernelCompilerFile-SystemScreen ResolutionSystem LayerMlc_test BenchmarksSystem Logs- nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 - Transparent Huge Pages: madvise - CPU Microcode: 0x1- itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Not affected + retbleed: Not affected + spec_store_bypass: Vulnerable + spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization + spectre_v2: Mitigation of Enhanced IBRS RSB filling PBRSB-eIBRS: SW sequence + srbds: Not affected + tsx_async_abort: Vulnerable: Clear buffers attempted no microcode; SMT Host state unknown

mlc_testintel-mlc: Peak Injection Bandwidth - Stream-Triad Likeintel-mlc: Peak Injection Bandwidth - 1:1 Reads-Writesintel-mlc: Max Bandwidth - 1:1 Reads-Writesintel-mlc: Idle Latencyintel-mlc: Peak Injection Bandwidth - All Readsintel-mlc: Max Bandwidth - 2:1 Reads-Writesintel-mlc: Max Bandwidth - Stream-Triad Likeintel-mlc: Peak Injection Bandwidth - 3:1 Reads-Writesintel-mlc: Max Bandwidth - 3:1 Reads-Writesintel-mlc: Peak Injection Bandwidth - 2:1 Reads-Writesintel-mlc: Max Bandwidth - All Readsmlc_testcompare80906.182731.488775.80123.058827.481068.9181023.2480385.681639.7878632.658851.0481128.082940.488959.73122.858893.481126.8180967.2180334.681591.8978608.558858.90OpenBenchmarking.org

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.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - Stream-Triad Likemlc_testcompare20K40K60K80K100KSE +/- 40.53, N = 3SE +/- 96.89, N = 380906.181128.0

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - 1:1 Reads-Writesmlc_testcompare20K40K60K80K100KSE +/- 12.84, N = 3SE +/- 154.17, N = 382731.482940.4

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Max Bandwidth - 1:1 Reads-Writesmlc_testcompare20K40K60K80K100KSE +/- 55.58, N = 3SE +/- 215.01, N = 388775.8088959.73

OpenBenchmarking.orgns, Fewer Is BetterIntel Memory Latency Checker 3.10Test: Idle Latencymlc_testcompare306090120150SE +/- 0.12, N = 3SE +/- 0.00, N = 3123.0122.8

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - All Readsmlc_testcompare13K26K39K52K65KSE +/- 6.24, N = 3SE +/- 61.04, N = 358827.458893.4

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Max Bandwidth - 2:1 Reads-Writesmlc_testcompare20K40K60K80K100KSE +/- 13.56, N = 3SE +/- 29.04, N = 381068.9181126.81

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Max Bandwidth - Stream-Triad Likecomparemlc_test20K40K60K80K100KSE +/- 82.30, N = 3SE +/- 93.84, N = 380967.2181023.24

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - 3:1 Reads-Writescomparemlc_test20K40K60K80K100KSE +/- 0.17, N = 3SE +/- 29.02, N = 380334.680385.6

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Max Bandwidth - 3:1 Reads-Writescomparemlc_test20K40K60K80K100KSE +/- 101.58, N = 3SE +/- 90.81, N = 381591.8981639.78

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - 2:1 Reads-Writescomparemlc_test20K40K60K80K100KSE +/- 19.90, N = 3SE +/- 62.56, N = 378608.578632.6

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Max Bandwidth - All Readsmlc_testcompare13K26K39K52K65KSE +/- 18.27, N = 3SE +/- 13.97, N = 358851.0458858.90

mlc_test

Kernel Notes: nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 - Transparent Huge Pages: madvise
Processor Notes: CPU Microcode: 0x1
Security Notes: itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Not affected + retbleed: Not affected + spec_store_bypass: Vulnerable + spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization + spectre_v2: Mitigation of Enhanced IBRS RSB filling PBRSB-eIBRS: SW sequence + srbds: Not affected + tsx_async_abort: Vulnerable: Clear buffers attempted no microcode; SMT Host state unknown

Testing initiated at 12 June 2023 02:27 by user .

compare

Processor: Intel Xeon Platinum 8475B (4 Cores / 8 Threads), Motherboard: Alibaba Cloud ECS (449e491 BIOS), Chipset: Intel 440FX 82441FX PMC, Memory: 1 x 16 GB RAM, Disk: 43GB Alibaba Cloud Elastic Block Storage, Graphics: Cirrus Logic GD 5446, Network: Red Hat Virtio device

OS: AlibabaCloud 3, Kernel: 5.10.134-13.1.al8.x86_64 (x86_64), Compiler: GCC 10.2.1 20200825, File-System: ext4, Screen Resolution: 1024x768, System Layer: KVM

Kernel Notes: nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 - Transparent Huge Pages: madvise
Processor Notes: CPU Microcode: 0x1
Security Notes: itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Not affected + retbleed: Not affected + spec_store_bypass: Vulnerable + spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization + spectre_v2: Mitigation of Enhanced IBRS RSB filling PBRSB-eIBRS: SW sequence + srbds: Not affected + tsx_async_abort: Vulnerable: Clear buffers attempted no microcode; SMT Host state unknown

Testing initiated at 12 June 2023 02:41 by user .