intelmemorydocker

Docker testing on Ubuntu 20.04.4 LTS 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 2308315-NE-INTELMEMO74
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
Performance Per
Dollar
Date
Run
  Test
  Duration
Intel Core i7-10610U - hyperv_fb - Microsoft Virtual
August 31 2023
  6 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):

Intel Core i7-10610U - hyperv_fb - Microsoft Virtual

Processor: Intel Core i7-10610U (4 Cores / 8 Threads), Motherboard: Microsoft Virtual Machine (Hyper-V UEFI v4.0 BIOS), Memory: 16GB, Disk: 69GB Virtual Disk, Graphics: hyperv_fb

OS: Ubuntu 20.04.4 LTS, Kernel: 5.15.49-linuxkit-pr (x86_64), Compiler: GCC 9.4.0, File-System: overlayfs, Screen Resolution: 1024x768, System Layer: Docker

Kernel Notes: Transparent Huge Pages: madvise
Processor Notes: CPU Microcode: 0xffffffff
Security Notes: itlb_multihit: KVM: Mitigation of VMX unsupported + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Vulnerable + spec_store_bypass: Vulnerable + spectre_v1: Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers + spectre_v2: Vulnerable IBPB: disabled STIBP: disabled + srbds: Unknown: Dependent on hypervisor status + tsx_async_abort: Mitigation of TSX disabled

intelmemorydockerOpenBenchmarking.orgPhoronix Test SuiteIntel Core i7-10610U (4 Cores / 8 Threads)Microsoft Virtual Machine (Hyper-V UEFI v4.0 BIOS)16GB69GB Virtual Diskhyperv_fbUbuntu 20.04.4 LTS5.15.49-linuxkit-pr (x86_64)GCC 9.4.0overlayfs1024x768DockerProcessorMotherboardMemoryDiskGraphicsOSKernelCompilerFile-SystemScreen ResolutionSystem LayerIntelmemorydocker BenchmarksSystem Logs- Transparent Huge Pages: madvise- CPU Microcode: 0xffffffff- itlb_multihit: KVM: Mitigation of VMX unsupported + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Vulnerable + spec_store_bypass: Vulnerable + spectre_v1: Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers + spectre_v2: Vulnerable IBPB: disabled STIBP: disabled + srbds: Unknown: Dependent on hypervisor status + tsx_async_abort: Mitigation of TSX disabled

intelmemorydockerintel-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 LikeIntel Core i7-10610U - hyperv_fb - Microsoft Virtual20963.522613.725603.028125.023969.3OpenBenchmarking.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 - All ReadsIntel Core i7-10610U - hyperv_fb - Microsoft Virtual4K8K12K16K20KSE +/- 200.87, N = 320963.5

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - 3:1 Reads-WritesIntel Core i7-10610U - hyperv_fb - Microsoft Virtual5K10K15K20K25KSE +/- 235.18, N = 322613.7

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - 2:1 Reads-WritesIntel Core i7-10610U - hyperv_fb - Microsoft Virtual5K10K15K20K25KSE +/- 241.17, N = 325603.0

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - 1:1 Reads-WritesIntel Core i7-10610U - hyperv_fb - Microsoft Virtual6K12K18K24K30KSE +/- 24.43, N = 328125.0

OpenBenchmarking.orgMB/s, More Is BetterIntel Memory Latency Checker 3.10Test: Peak Injection Bandwidth - Stream-Triad LikeIntel Core i7-10610U - hyperv_fb - Microsoft Virtual5K10K15K20K25KSE +/- 126.82, N = 323969.3

Intel Core i7-10610U - hyperv_fb - Microsoft Virtual

Processor: Intel Core i7-10610U (4 Cores / 8 Threads), Motherboard: Microsoft Virtual Machine (Hyper-V UEFI v4.0 BIOS), Memory: 16GB, Disk: 69GB Virtual Disk, Graphics: hyperv_fb

OS: Ubuntu 20.04.4 LTS, Kernel: 5.15.49-linuxkit-pr (x86_64), Compiler: GCC 9.4.0, File-System: overlayfs, Screen Resolution: 1024x768, System Layer: Docker

Kernel Notes: Transparent Huge Pages: madvise
Processor Notes: CPU Microcode: 0xffffffff
Security Notes: itlb_multihit: KVM: Mitigation of VMX unsupported + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Vulnerable + spec_store_bypass: Vulnerable + spectre_v1: Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers + spectre_v2: Vulnerable IBPB: disabled STIBP: disabled + srbds: Unknown: Dependent on hypervisor status + tsx_async_abort: Mitigation of TSX disabled

Testing initiated at 31 August 2023 10:42 by user root.