CPU performance test results in three scenarios
Hello, I recently conducted a test to compare the CPU performance of a physical machine, a high performance VM (pass-through CPU, PIN CPU), and a common VM. Here are the results: 1. Physical machine: # sysbench --test=cpu --cpu-max-prime=100000000 --threads=2 run WARNING: the --test option is deprecated. You can pass a script name or path on the command line without any options. sysbench 1.0.17 (using system LuaJIT 2.0.4) Running the test with following options: Number of threads: 2 Initializing random number generator from current time Prime numbers limit: 100000000 Initializing worker threads... Threads started! CPU speed: events per second: 0.01 General statistics: total time: 346.0588s total number of events: 2 Latency (ms): min: 345943.52 avg: 346001.09 max: 346058.65 95th percentile: 100000.00 sum: 692002.17 Threads fairness: events (avg/stddev): 1.0000/0.00 execution time (avg/stddev): 346.0011/0.06 2. High Performance VM: # sysbench --test=cpu --cpu-max-prime=100000000 --threads=2 run WARNING: the --test option is deprecated. You can pass a script name or path on the command line without any options. sysbench 1.0.17 (using system LuaJIT 2.0.4) Running the test with following options: Number of threads: 2 Initializing random number generator from current time Prime numbers limit: 100000000 Initializing worker threads... Threads started! CPU speed: events per second: 0.01 General statistics: total time: 351.8625s total number of events: 2 Latency (ms): min: 351416.59 avg: 351639.01 max: 351861.43 95th percentile: 100000.00 sum: 703278.02 Threads fairness: events (avg/stddev): 1.0000/0.00 execution time (avg/stddev): 351.6390/0.22 3. Common VM: # sysbench --test=cpu --cpu-max-prime=100000000 --threads=2 run WARNING: the --test option is deprecated. You can pass a script name or path on the command line without any options. sysbench 1.0.17 (using system LuaJIT 2.0.4) Running the test with following options: Number of threads: 2 Initializing random number generator from current time Prime numbers limit: 100000000 Initializing worker threads... Threads started! CPU speed: events per second: 0.01 General statistics: total time: 354.9108s total number of events: 2 Latency (ms): min: 354761.26 avg: 354835.99 max: 354910.73 95th percentile: 100000.00 sum: 709671.99 Threads fairness: events (avg/stddev): 1.0000/0.00 execution time (avg/stddev): 354.8360/0.07 Result: There is little difference in CPU performance between these three scenarios, so why distinguish between high performance and regular virtual machines? I don't think it makes much sense.
Have you done CPU passthrough in a high-performance virtual machine? What are the NUMA settings? As far as I know, CPU passthrough is only available in the high performance virtual machine and certain CPU flags are also applied
CPU passthrough and cpu pinning are important for cpu lattency workloads luke for example SAP HANA or workloads that benefit from the extra (cpu passthrough) instructions. Best Regards,Strahil Nikolov On Mon, Aug 2, 2021 at 13:13, Patrick Lomakin<patrick.lomakin@gmail.com> wrote: Have you done CPU passthrough in a high-performance virtual machine? What are the NUMA settings? As far as I know, CPU passthrough is only available in the high performance virtual machine and certain CPU flags are also applied _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AUDKY7CRTQUHUN...
On my OLVM environment, I assigned a high-performance virtual machine with CPU passthrough and CPU Pin Settings, but why did I find NUMA unavailable when configuring it? The physical host cpu info: [root@kvms3 ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 142 Model name: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz Stepping: 10 CPU MHz: 3934.702 CPU max MHz: 4200.0000 CPU min MHz: 400.0000 BogoMIPS: 4199.88 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d The vm cpu info: [root@testhigh ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 2 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 142 Model name: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz Stepping: 10 CPU MHz: 2111.998 BogoMIPS: 4223.99 Virtualization: VT-x Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K L3 cache: 16384K NUMA node0 CPU(s): 0,1 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves arat umip md_clear arch_capabilities -----Original Message----- From: users-bounces@ovirt.org <users-bounces@ovirt.org> On Behalf Of Patrick Lomakin Sent: Monday, August 2, 2021 6:13 PM To: users@ovirt.org Subject: [ovirt-users] Re: CPU performance test results in three scenarios Have you done CPU passthrough in a high-performance virtual machine? What are the NUMA settings? As far as I know, CPU passthrough is only available in the high performance virtual machine and certain CPU flags are also applied _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AUDKY7CRTQUHUN...
participants (3)
-
Patrick Lomakin -
Strahil Nikolov -
Tommy Sway