All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
/proc/cpuinfo is different from lscpu / lshw
Hello LET community,
i'm not really used to this kind of behavior, providers i normally use always show real CPU info. Here, i get "QEMU Virtual CPU" and i see difference between different commands to give informations about CPU.
Here the /proc/cpuinfo:
root@mc1:~# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 6
model name : QEMU Virtual CPU version 2.5+
stepping : 3
microcode : 0x1000065
cpu MHz : 3792.874
cache size : 512 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm nopl cpuid pni cx16 x2apic hypervisor lahf_lm svm 3dnowprefetch vmmcall
bugs : fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
bogomips : 7585.74
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
Here the lshw -C processor:
root@mc1:~# lshw -C processor
*-cpu:0
description: CPU
product: QEMU Virtual CPU version 2.5+
vendor: Advanced Micro Devices [AMD]
physical id: 400
bus info: cpu@0
version: pc-i440fx-2.11
slot: CPU 0
size: 2GHz
capacity: 2GHz
width: 64 bits
capabilities: fpu fpu_exception wp de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx x86-64 nopl cpuid pni cx16 x2apic hypervisor lahf_lm svm 3dnowprefetch vmmcall
configuration: cores=1 enabledcores=1 threads=1
Here the lscpu:
root@mc1:~# 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: AuthenticAMD
CPU family: 6
Model: 6
Model name: QEMU Virtual CPU version 2.5+
Stepping: 3
CPU MHz: 3792.874
BogoMIPS: 7585.74
Virtualization: AMD-V
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
L3 cache: 16384K
NUMA node0 CPU(s): 0,1
Flags: fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm nopl cpuid pni cx16 x2apic hypervisor lahf_lm svm 3dnowprefetch vmmcall
And here the dmidecode:
Handle 0x0400, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 0
Type: Central Processor
Family: Other
Manufacturer: QEMU
ID: 63 06 00 00 FD FB 8B 07
Version: pc-i440fx-2.11
Voltage: Unknown
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 1
Core Enabled: 1
Thread Count: 1
Characteristics: None
Is it normal to show 3.7GHz and 2GHz at the same time? I've tried to search on google but probably i don't use good keywords for that...
Is there a way to better check this?
One last question: when we see frequency, i've seen that we often see the "base" frequency but never the "boost" frequency. Does providers limits access to the "boost"? I mean if a cpu is 3.7GHz to 4.4GHz, i see 3.7GHz but can i go to 4.4GHz? How can i check it?
Thanks a lot, i feel confused with this...
Comments
Check it with unixbench what it's really capable of. Words are often misleading.
Good idea, i did a test already with GeekBench 5:
https://browser.geekbench.com/v5/cpu/2541406
@o_be_one, if it is of any help, I have the same differing MHz outputs with my BuyVM Ryzen VPS. They do not hide CPU infos, so I guess that the behavior you are observing is normal.
Either badly reported values, or these CPUs have low idling frequencies.
cat /proc/cpuinfo
(cutting next outputs to the relevant infos only)
lshw -C processor
dmidecode
lscpu
959 single core is a goody
Thanks you, it's a perfect comparison i think. @Francisco maybe you can add an expert point of view? Could be interesting to know more ^^. Thanks!
I also know @seriesn with knowledge in Ryzen, could be also really interesting to have your input ^^.
My BuyVM's benches with bench.sh and unixbench shows that they all 3 are very capable CPU's and probably is overkill for a DNS server, but it's nice to have a CPU power to handle possible spikes of traffic. As for stability - just started 2 days ago outer pings monitoring and so far not any single icmp4 packet has not been lost. Great vpses and network, Francisco! Not even mention of anycast yet! More on that later.