Ubuntu get actual current CPU clock speed The Next CEO of Stack OverflowIncorrect CPU clock...

Describing a person. What needs to be mentioned?

Failed to fetch jessie backports repository

Where to find order of arguments for default functions

What does this shorthand mean?

Term for the "extreme-extension" version of a straw man fallacy?

Should I tutor a student who I know has cheated on their homework?

Are there languages with no euphemisms?

Trouble understanding the speech of overseas colleagues

Example of a Mathematician/Physicist whose Other Publications during their PhD eclipsed their PhD Thesis

What do "high sea" and "carry" mean in this sentence?

Why do professional authors make "consistency" mistakes? And how to avoid them?

Is it my responsibility to learn a new technology in my own time my employer wants to implement?

How to count occurrences of text in a file?

What's the point of interval inversion?

Implement the Thanos sorting algorithm

How do I solve this limit?

Why didn't Theresa May consult with Parliament before negotiating a deal with the EU?

Opposite of a diet

Too much space between section and text in a twocolumn document

Go Pregnant or Go Home

Is the concept of a "numerable" fiber bundle really useful or an empty generalization?

Rotate a column

Anatomically Correct Strange Women In Ponds Distributing Swords

How do spells that require an ability check vs. the caster's spell save DC work?



Ubuntu get actual current CPU clock speed



The Next CEO of Stack OverflowIncorrect CPU clock speed?Ubuntu 14.04 lost cores on AMD CPUXubuntu pentium 4 not enough CPU for development/usr/sbin/pwmconfig: There are no fan-capable sensor modules installedUbuntu crashes with blank screenVirtualbox VT-x error though virtualization seems enabled already14.04 & 16.04 Lenovo 4 GB RAM installed, 3.3 Gb detectedUbuntu 16.04 server unable to detect intel graphics on I3 6100Ubuntu with Ryzen 2500u Processor speed capped at 2GHzUbuntu 18.04 Xeon E5450 on p43-a7 socket 775 only one core working












3















(Irrelevant) Background



My Dell XPS 15 9550 laptop is slow; typing in text boxes doesn't keep up with me, moving around google maps is undoable, and javascript popups are slow when I browse. The same holds for development websites I run locally.



I noticed that the CPU might be throttled at 800Mhz. So I started investigating CPU reports:




  • Linux /proc/cpuinfo reports ~800MHz on all 8 threads

  • Windows task manager stated 0.8GHz

  • Open Hardware Monitor in windows reports 800MHz on all 8 threads, and 100MHz bus speed.


I called Dell, and they suggested to update the Bios and disable SpeedStep and C-States. I did, afterwards the windows task manager started reporting 2.6GHz and so did the bios, but the Open Hardware Monitor in windows still said 800MHz CPU and 100Mhz bus.



So the numbers in Windows seem inconsistent, but I frankly mostly care about Ubuntu. After the bios changes, Ubuntu still feels slow.



Question



I want to know at which speed my CPU or cores actually run. So made sure the cores had some work to do



for i in `seq 5`; do (echo "i=0"; echo "while True: i=1+1") | python& done


Now 5 threads are full active in the task manager; a reason for the performance governor to scale up the cores. What I see is this:



lshw



$ sudo lshw -c cpu
*-cpu
description: CPU
product: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
vendor: Intel Corp.
physical id: 3c
bus info: cpu@0
version: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 799MHz # suggests the current speed is 800MHz
capacity: 3500MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp 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 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 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 epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp cpufreq
configuration: cores=4 threads=8


/proc/cpuinfo



$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 94
model name : Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
stepping : 3
microcode : 0x9e
cpu MHz : 799.906
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 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 epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp
bugs :
bogomips : 5183.76
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

# Repeated 8 times for all threads, cpu MHz around 800MHz for all


dmidecode



$ sudo dmidecode -t processor
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x003C, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Core i7
Manufacturer: Intel(R) Corporation
ID: E3 06 05 00 FF FB EB BF
Signature: Type 0, Family 6, Model 94, Stepping 3
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Voltage: 0.6 V
External Clock: 100 MHz
Max Speed: 2600 MHz
Current Speed: 2600 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0039
L2 Cache Handle: 0x003A
L3 Cache Handle: 0x003B
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 4
Thread Count: 8
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance Control


Here /proc/cpuinfo and lshw suggest the actual CPU speed is 800MHz, this is backed up by how slow my machine is. However, `dmidecode says the Current Speed is 2600MHz, and so does my BIOS. Why are this numbers inconsistent? Is there an empirical way, check how long a CPU needs to calculate something, to guess the CPU speed? (800MHz should be quite distinguishable from 2600MHz)



Moreover, Open Hardware Monitor also reports 800Mhz, while Windows Task Manager reports 2.6GHz.



Obviously, any suggestions on how to to solve the CPU throttling would be well appreciated. I already found the 'open laptop, unmount battery for some minutes' and 'completely drain battery, leave uncharged for some minutes' solutions. Will still need to try those.










share|improve this question























  • With the intel_pstate CPU frequency scaling driver what is reported by /proc/cpuinfo will be the correct CPU frequency as seen over the last sample interval. With the acpi-cpufreq CPU frequency scaling driver what is reported by /proc/cpuinfo is the frequency that was asked for, and might not be the actual frequency. You can check which driver you are using via cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver

    – Doug Smythies
    May 18 '17 at 15:15
















3















(Irrelevant) Background



My Dell XPS 15 9550 laptop is slow; typing in text boxes doesn't keep up with me, moving around google maps is undoable, and javascript popups are slow when I browse. The same holds for development websites I run locally.



I noticed that the CPU might be throttled at 800Mhz. So I started investigating CPU reports:




  • Linux /proc/cpuinfo reports ~800MHz on all 8 threads

  • Windows task manager stated 0.8GHz

  • Open Hardware Monitor in windows reports 800MHz on all 8 threads, and 100MHz bus speed.


I called Dell, and they suggested to update the Bios and disable SpeedStep and C-States. I did, afterwards the windows task manager started reporting 2.6GHz and so did the bios, but the Open Hardware Monitor in windows still said 800MHz CPU and 100Mhz bus.



So the numbers in Windows seem inconsistent, but I frankly mostly care about Ubuntu. After the bios changes, Ubuntu still feels slow.



Question



I want to know at which speed my CPU or cores actually run. So made sure the cores had some work to do



for i in `seq 5`; do (echo "i=0"; echo "while True: i=1+1") | python& done


Now 5 threads are full active in the task manager; a reason for the performance governor to scale up the cores. What I see is this:



lshw



$ sudo lshw -c cpu
*-cpu
description: CPU
product: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
vendor: Intel Corp.
physical id: 3c
bus info: cpu@0
version: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 799MHz # suggests the current speed is 800MHz
capacity: 3500MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp 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 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 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 epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp cpufreq
configuration: cores=4 threads=8


/proc/cpuinfo



$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 94
model name : Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
stepping : 3
microcode : 0x9e
cpu MHz : 799.906
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 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 epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp
bugs :
bogomips : 5183.76
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

# Repeated 8 times for all threads, cpu MHz around 800MHz for all


dmidecode



$ sudo dmidecode -t processor
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x003C, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Core i7
Manufacturer: Intel(R) Corporation
ID: E3 06 05 00 FF FB EB BF
Signature: Type 0, Family 6, Model 94, Stepping 3
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Voltage: 0.6 V
External Clock: 100 MHz
Max Speed: 2600 MHz
Current Speed: 2600 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0039
L2 Cache Handle: 0x003A
L3 Cache Handle: 0x003B
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 4
Thread Count: 8
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance Control


Here /proc/cpuinfo and lshw suggest the actual CPU speed is 800MHz, this is backed up by how slow my machine is. However, `dmidecode says the Current Speed is 2600MHz, and so does my BIOS. Why are this numbers inconsistent? Is there an empirical way, check how long a CPU needs to calculate something, to guess the CPU speed? (800MHz should be quite distinguishable from 2600MHz)



Moreover, Open Hardware Monitor also reports 800Mhz, while Windows Task Manager reports 2.6GHz.



Obviously, any suggestions on how to to solve the CPU throttling would be well appreciated. I already found the 'open laptop, unmount battery for some minutes' and 'completely drain battery, leave uncharged for some minutes' solutions. Will still need to try those.










share|improve this question























  • With the intel_pstate CPU frequency scaling driver what is reported by /proc/cpuinfo will be the correct CPU frequency as seen over the last sample interval. With the acpi-cpufreq CPU frequency scaling driver what is reported by /proc/cpuinfo is the frequency that was asked for, and might not be the actual frequency. You can check which driver you are using via cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver

    – Doug Smythies
    May 18 '17 at 15:15














3












3








3








(Irrelevant) Background



My Dell XPS 15 9550 laptop is slow; typing in text boxes doesn't keep up with me, moving around google maps is undoable, and javascript popups are slow when I browse. The same holds for development websites I run locally.



I noticed that the CPU might be throttled at 800Mhz. So I started investigating CPU reports:




  • Linux /proc/cpuinfo reports ~800MHz on all 8 threads

  • Windows task manager stated 0.8GHz

  • Open Hardware Monitor in windows reports 800MHz on all 8 threads, and 100MHz bus speed.


I called Dell, and they suggested to update the Bios and disable SpeedStep and C-States. I did, afterwards the windows task manager started reporting 2.6GHz and so did the bios, but the Open Hardware Monitor in windows still said 800MHz CPU and 100Mhz bus.



So the numbers in Windows seem inconsistent, but I frankly mostly care about Ubuntu. After the bios changes, Ubuntu still feels slow.



Question



I want to know at which speed my CPU or cores actually run. So made sure the cores had some work to do



for i in `seq 5`; do (echo "i=0"; echo "while True: i=1+1") | python& done


Now 5 threads are full active in the task manager; a reason for the performance governor to scale up the cores. What I see is this:



lshw



$ sudo lshw -c cpu
*-cpu
description: CPU
product: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
vendor: Intel Corp.
physical id: 3c
bus info: cpu@0
version: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 799MHz # suggests the current speed is 800MHz
capacity: 3500MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp 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 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 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 epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp cpufreq
configuration: cores=4 threads=8


/proc/cpuinfo



$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 94
model name : Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
stepping : 3
microcode : 0x9e
cpu MHz : 799.906
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 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 epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp
bugs :
bogomips : 5183.76
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

# Repeated 8 times for all threads, cpu MHz around 800MHz for all


dmidecode



$ sudo dmidecode -t processor
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x003C, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Core i7
Manufacturer: Intel(R) Corporation
ID: E3 06 05 00 FF FB EB BF
Signature: Type 0, Family 6, Model 94, Stepping 3
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Voltage: 0.6 V
External Clock: 100 MHz
Max Speed: 2600 MHz
Current Speed: 2600 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0039
L2 Cache Handle: 0x003A
L3 Cache Handle: 0x003B
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 4
Thread Count: 8
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance Control


Here /proc/cpuinfo and lshw suggest the actual CPU speed is 800MHz, this is backed up by how slow my machine is. However, `dmidecode says the Current Speed is 2600MHz, and so does my BIOS. Why are this numbers inconsistent? Is there an empirical way, check how long a CPU needs to calculate something, to guess the CPU speed? (800MHz should be quite distinguishable from 2600MHz)



Moreover, Open Hardware Monitor also reports 800Mhz, while Windows Task Manager reports 2.6GHz.



Obviously, any suggestions on how to to solve the CPU throttling would be well appreciated. I already found the 'open laptop, unmount battery for some minutes' and 'completely drain battery, leave uncharged for some minutes' solutions. Will still need to try those.










share|improve this question














(Irrelevant) Background



My Dell XPS 15 9550 laptop is slow; typing in text boxes doesn't keep up with me, moving around google maps is undoable, and javascript popups are slow when I browse. The same holds for development websites I run locally.



I noticed that the CPU might be throttled at 800Mhz. So I started investigating CPU reports:




  • Linux /proc/cpuinfo reports ~800MHz on all 8 threads

  • Windows task manager stated 0.8GHz

  • Open Hardware Monitor in windows reports 800MHz on all 8 threads, and 100MHz bus speed.


I called Dell, and they suggested to update the Bios and disable SpeedStep and C-States. I did, afterwards the windows task manager started reporting 2.6GHz and so did the bios, but the Open Hardware Monitor in windows still said 800MHz CPU and 100Mhz bus.



So the numbers in Windows seem inconsistent, but I frankly mostly care about Ubuntu. After the bios changes, Ubuntu still feels slow.



Question



I want to know at which speed my CPU or cores actually run. So made sure the cores had some work to do



for i in `seq 5`; do (echo "i=0"; echo "while True: i=1+1") | python& done


Now 5 threads are full active in the task manager; a reason for the performance governor to scale up the cores. What I see is this:



lshw



$ sudo lshw -c cpu
*-cpu
description: CPU
product: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
vendor: Intel Corp.
physical id: 3c
bus info: cpu@0
version: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 799MHz # suggests the current speed is 800MHz
capacity: 3500MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp 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 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 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 epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp cpufreq
configuration: cores=4 threads=8


/proc/cpuinfo



$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 94
model name : Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
stepping : 3
microcode : 0x9e
cpu MHz : 799.906
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 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 epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp
bugs :
bogomips : 5183.76
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

# Repeated 8 times for all threads, cpu MHz around 800MHz for all


dmidecode



$ sudo dmidecode -t processor
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x003C, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Core i7
Manufacturer: Intel(R) Corporation
ID: E3 06 05 00 FF FB EB BF
Signature: Type 0, Family 6, Model 94, Stepping 3
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Voltage: 0.6 V
External Clock: 100 MHz
Max Speed: 2600 MHz
Current Speed: 2600 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0039
L2 Cache Handle: 0x003A
L3 Cache Handle: 0x003B
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 4
Thread Count: 8
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance Control


Here /proc/cpuinfo and lshw suggest the actual CPU speed is 800MHz, this is backed up by how slow my machine is. However, `dmidecode says the Current Speed is 2600MHz, and so does my BIOS. Why are this numbers inconsistent? Is there an empirical way, check how long a CPU needs to calculate something, to guess the CPU speed? (800MHz should be quite distinguishable from 2600MHz)



Moreover, Open Hardware Monitor also reports 800Mhz, while Windows Task Manager reports 2.6GHz.



Obviously, any suggestions on how to to solve the CPU throttling would be well appreciated. I already found the 'open laptop, unmount battery for some minutes' and 'completely drain battery, leave uncharged for some minutes' solutions. Will still need to try those.







16.04 cpu






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 18 '17 at 9:04









HerbertHerbert

123118




123118













  • With the intel_pstate CPU frequency scaling driver what is reported by /proc/cpuinfo will be the correct CPU frequency as seen over the last sample interval. With the acpi-cpufreq CPU frequency scaling driver what is reported by /proc/cpuinfo is the frequency that was asked for, and might not be the actual frequency. You can check which driver you are using via cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver

    – Doug Smythies
    May 18 '17 at 15:15



















  • With the intel_pstate CPU frequency scaling driver what is reported by /proc/cpuinfo will be the correct CPU frequency as seen over the last sample interval. With the acpi-cpufreq CPU frequency scaling driver what is reported by /proc/cpuinfo is the frequency that was asked for, and might not be the actual frequency. You can check which driver you are using via cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver

    – Doug Smythies
    May 18 '17 at 15:15

















With the intel_pstate CPU frequency scaling driver what is reported by /proc/cpuinfo will be the correct CPU frequency as seen over the last sample interval. With the acpi-cpufreq CPU frequency scaling driver what is reported by /proc/cpuinfo is the frequency that was asked for, and might not be the actual frequency. You can check which driver you are using via cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver

– Doug Smythies
May 18 '17 at 15:15





With the intel_pstate CPU frequency scaling driver what is reported by /proc/cpuinfo will be the correct CPU frequency as seen over the last sample interval. With the acpi-cpufreq CPU frequency scaling driver what is reported by /proc/cpuinfo is the frequency that was asked for, and might not be the actual frequency. You can check which driver you are using via cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver

– Doug Smythies
May 18 '17 at 15:15










2 Answers
2






active

oldest

votes


















2














Use the command:



lscpu


To know all your CPU Specs:



To get the specific frequency of your CPU use the command with a grep like so:



lscpu | grep MHz


It will give you output like:



CPU MHz:               2723.789


To see realtime CPU speeds fluctuation use :



watch -n1 "lscpu | grep MHz | awk '{print $1}'";





share|improve this answer
























  • This does not explain the inconsistent reporting. I solved the issue, and my laptop runs a lot faster now suggesting that /proc/cpuinfo was right. Nevertheless, why did dmidecode say Current Speed: 2600 MHz? I don't believe this is due to fluctuations because I was running 5 while-true loops, maximizing CPU utilization for 5 threads; a fluctuation between 800MHz and 2600MHz on such a load would be strange. Moreover, /proc/cpuinfo reports higher MHz's after the fix, and my machine feels also much faster, suggesting the machine was running at 800MHz consistently, and never 2600MHz.

    – Herbert
    May 18 '17 at 14:06











  • Hi @Herbert how do you fixed that? I have with a similar problem.

    – Joao Gilberto Magalhaes
    Mar 14 '18 at 16:48











  • It turned out to be a problem with/bug in my Dell XPS 15, namely that the CPU would throttle at 800MHz at some point, regardless of settings in the BIOS. I spoke with customer support and after ruling out some more trivial things, the support agent allowed me to open up the laptop, disconnect the battery from the main board and reconnect it again after 30 seconds. This resolved the issue, but it did happen twice up until now. Since I work at a high performance computing center of a university, I had the luxury to have an electronics expert to do so.

    – Herbert
    Mar 15 '18 at 8:41





















0














Your system is probably using intel_pstate driver.



Setting this driver's governor is very easy. To set all CPUs to maximum frequency, just use the following command:



echo 100 | sudo tee /sys/devices/system/cpu/intel_pstate/min_perf_pct


To do the opposite, and force low power on the CPUs, issue:



echo 20 | sudo tee /sys/devices/system/cpu/intel_pstate/max_perf_pct


Where 20 is the percentage of maximum performance you want to allow. Setting this to 10% will probably result in extremely sluggish GUI, but you can try and see.



Sources: kernel.org





share
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f916382%2fubuntu-get-actual-current-cpu-clock-speed%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    Use the command:



    lscpu


    To know all your CPU Specs:



    To get the specific frequency of your CPU use the command with a grep like so:



    lscpu | grep MHz


    It will give you output like:



    CPU MHz:               2723.789


    To see realtime CPU speeds fluctuation use :



    watch -n1 "lscpu | grep MHz | awk '{print $1}'";





    share|improve this answer
























    • This does not explain the inconsistent reporting. I solved the issue, and my laptop runs a lot faster now suggesting that /proc/cpuinfo was right. Nevertheless, why did dmidecode say Current Speed: 2600 MHz? I don't believe this is due to fluctuations because I was running 5 while-true loops, maximizing CPU utilization for 5 threads; a fluctuation between 800MHz and 2600MHz on such a load would be strange. Moreover, /proc/cpuinfo reports higher MHz's after the fix, and my machine feels also much faster, suggesting the machine was running at 800MHz consistently, and never 2600MHz.

      – Herbert
      May 18 '17 at 14:06











    • Hi @Herbert how do you fixed that? I have with a similar problem.

      – Joao Gilberto Magalhaes
      Mar 14 '18 at 16:48











    • It turned out to be a problem with/bug in my Dell XPS 15, namely that the CPU would throttle at 800MHz at some point, regardless of settings in the BIOS. I spoke with customer support and after ruling out some more trivial things, the support agent allowed me to open up the laptop, disconnect the battery from the main board and reconnect it again after 30 seconds. This resolved the issue, but it did happen twice up until now. Since I work at a high performance computing center of a university, I had the luxury to have an electronics expert to do so.

      – Herbert
      Mar 15 '18 at 8:41


















    2














    Use the command:



    lscpu


    To know all your CPU Specs:



    To get the specific frequency of your CPU use the command with a grep like so:



    lscpu | grep MHz


    It will give you output like:



    CPU MHz:               2723.789


    To see realtime CPU speeds fluctuation use :



    watch -n1 "lscpu | grep MHz | awk '{print $1}'";





    share|improve this answer
























    • This does not explain the inconsistent reporting. I solved the issue, and my laptop runs a lot faster now suggesting that /proc/cpuinfo was right. Nevertheless, why did dmidecode say Current Speed: 2600 MHz? I don't believe this is due to fluctuations because I was running 5 while-true loops, maximizing CPU utilization for 5 threads; a fluctuation between 800MHz and 2600MHz on such a load would be strange. Moreover, /proc/cpuinfo reports higher MHz's after the fix, and my machine feels also much faster, suggesting the machine was running at 800MHz consistently, and never 2600MHz.

      – Herbert
      May 18 '17 at 14:06











    • Hi @Herbert how do you fixed that? I have with a similar problem.

      – Joao Gilberto Magalhaes
      Mar 14 '18 at 16:48











    • It turned out to be a problem with/bug in my Dell XPS 15, namely that the CPU would throttle at 800MHz at some point, regardless of settings in the BIOS. I spoke with customer support and after ruling out some more trivial things, the support agent allowed me to open up the laptop, disconnect the battery from the main board and reconnect it again after 30 seconds. This resolved the issue, but it did happen twice up until now. Since I work at a high performance computing center of a university, I had the luxury to have an electronics expert to do so.

      – Herbert
      Mar 15 '18 at 8:41
















    2












    2








    2







    Use the command:



    lscpu


    To know all your CPU Specs:



    To get the specific frequency of your CPU use the command with a grep like so:



    lscpu | grep MHz


    It will give you output like:



    CPU MHz:               2723.789


    To see realtime CPU speeds fluctuation use :



    watch -n1 "lscpu | grep MHz | awk '{print $1}'";





    share|improve this answer













    Use the command:



    lscpu


    To know all your CPU Specs:



    To get the specific frequency of your CPU use the command with a grep like so:



    lscpu | grep MHz


    It will give you output like:



    CPU MHz:               2723.789


    To see realtime CPU speeds fluctuation use :



    watch -n1 "lscpu | grep MHz | awk '{print $1}'";






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered May 18 '17 at 9:17









    Shakti PhartiyalShakti Phartiyal

    390212




    390212













    • This does not explain the inconsistent reporting. I solved the issue, and my laptop runs a lot faster now suggesting that /proc/cpuinfo was right. Nevertheless, why did dmidecode say Current Speed: 2600 MHz? I don't believe this is due to fluctuations because I was running 5 while-true loops, maximizing CPU utilization for 5 threads; a fluctuation between 800MHz and 2600MHz on such a load would be strange. Moreover, /proc/cpuinfo reports higher MHz's after the fix, and my machine feels also much faster, suggesting the machine was running at 800MHz consistently, and never 2600MHz.

      – Herbert
      May 18 '17 at 14:06











    • Hi @Herbert how do you fixed that? I have with a similar problem.

      – Joao Gilberto Magalhaes
      Mar 14 '18 at 16:48











    • It turned out to be a problem with/bug in my Dell XPS 15, namely that the CPU would throttle at 800MHz at some point, regardless of settings in the BIOS. I spoke with customer support and after ruling out some more trivial things, the support agent allowed me to open up the laptop, disconnect the battery from the main board and reconnect it again after 30 seconds. This resolved the issue, but it did happen twice up until now. Since I work at a high performance computing center of a university, I had the luxury to have an electronics expert to do so.

      – Herbert
      Mar 15 '18 at 8:41





















    • This does not explain the inconsistent reporting. I solved the issue, and my laptop runs a lot faster now suggesting that /proc/cpuinfo was right. Nevertheless, why did dmidecode say Current Speed: 2600 MHz? I don't believe this is due to fluctuations because I was running 5 while-true loops, maximizing CPU utilization for 5 threads; a fluctuation between 800MHz and 2600MHz on such a load would be strange. Moreover, /proc/cpuinfo reports higher MHz's after the fix, and my machine feels also much faster, suggesting the machine was running at 800MHz consistently, and never 2600MHz.

      – Herbert
      May 18 '17 at 14:06











    • Hi @Herbert how do you fixed that? I have with a similar problem.

      – Joao Gilberto Magalhaes
      Mar 14 '18 at 16:48











    • It turned out to be a problem with/bug in my Dell XPS 15, namely that the CPU would throttle at 800MHz at some point, regardless of settings in the BIOS. I spoke with customer support and after ruling out some more trivial things, the support agent allowed me to open up the laptop, disconnect the battery from the main board and reconnect it again after 30 seconds. This resolved the issue, but it did happen twice up until now. Since I work at a high performance computing center of a university, I had the luxury to have an electronics expert to do so.

      – Herbert
      Mar 15 '18 at 8:41



















    This does not explain the inconsistent reporting. I solved the issue, and my laptop runs a lot faster now suggesting that /proc/cpuinfo was right. Nevertheless, why did dmidecode say Current Speed: 2600 MHz? I don't believe this is due to fluctuations because I was running 5 while-true loops, maximizing CPU utilization for 5 threads; a fluctuation between 800MHz and 2600MHz on such a load would be strange. Moreover, /proc/cpuinfo reports higher MHz's after the fix, and my machine feels also much faster, suggesting the machine was running at 800MHz consistently, and never 2600MHz.

    – Herbert
    May 18 '17 at 14:06





    This does not explain the inconsistent reporting. I solved the issue, and my laptop runs a lot faster now suggesting that /proc/cpuinfo was right. Nevertheless, why did dmidecode say Current Speed: 2600 MHz? I don't believe this is due to fluctuations because I was running 5 while-true loops, maximizing CPU utilization for 5 threads; a fluctuation between 800MHz and 2600MHz on such a load would be strange. Moreover, /proc/cpuinfo reports higher MHz's after the fix, and my machine feels also much faster, suggesting the machine was running at 800MHz consistently, and never 2600MHz.

    – Herbert
    May 18 '17 at 14:06













    Hi @Herbert how do you fixed that? I have with a similar problem.

    – Joao Gilberto Magalhaes
    Mar 14 '18 at 16:48





    Hi @Herbert how do you fixed that? I have with a similar problem.

    – Joao Gilberto Magalhaes
    Mar 14 '18 at 16:48













    It turned out to be a problem with/bug in my Dell XPS 15, namely that the CPU would throttle at 800MHz at some point, regardless of settings in the BIOS. I spoke with customer support and after ruling out some more trivial things, the support agent allowed me to open up the laptop, disconnect the battery from the main board and reconnect it again after 30 seconds. This resolved the issue, but it did happen twice up until now. Since I work at a high performance computing center of a university, I had the luxury to have an electronics expert to do so.

    – Herbert
    Mar 15 '18 at 8:41







    It turned out to be a problem with/bug in my Dell XPS 15, namely that the CPU would throttle at 800MHz at some point, regardless of settings in the BIOS. I spoke with customer support and after ruling out some more trivial things, the support agent allowed me to open up the laptop, disconnect the battery from the main board and reconnect it again after 30 seconds. This resolved the issue, but it did happen twice up until now. Since I work at a high performance computing center of a university, I had the luxury to have an electronics expert to do so.

    – Herbert
    Mar 15 '18 at 8:41















    0














    Your system is probably using intel_pstate driver.



    Setting this driver's governor is very easy. To set all CPUs to maximum frequency, just use the following command:



    echo 100 | sudo tee /sys/devices/system/cpu/intel_pstate/min_perf_pct


    To do the opposite, and force low power on the CPUs, issue:



    echo 20 | sudo tee /sys/devices/system/cpu/intel_pstate/max_perf_pct


    Where 20 is the percentage of maximum performance you want to allow. Setting this to 10% will probably result in extremely sluggish GUI, but you can try and see.



    Sources: kernel.org





    share




























      0














      Your system is probably using intel_pstate driver.



      Setting this driver's governor is very easy. To set all CPUs to maximum frequency, just use the following command:



      echo 100 | sudo tee /sys/devices/system/cpu/intel_pstate/min_perf_pct


      To do the opposite, and force low power on the CPUs, issue:



      echo 20 | sudo tee /sys/devices/system/cpu/intel_pstate/max_perf_pct


      Where 20 is the percentage of maximum performance you want to allow. Setting this to 10% will probably result in extremely sluggish GUI, but you can try and see.



      Sources: kernel.org





      share


























        0












        0








        0







        Your system is probably using intel_pstate driver.



        Setting this driver's governor is very easy. To set all CPUs to maximum frequency, just use the following command:



        echo 100 | sudo tee /sys/devices/system/cpu/intel_pstate/min_perf_pct


        To do the opposite, and force low power on the CPUs, issue:



        echo 20 | sudo tee /sys/devices/system/cpu/intel_pstate/max_perf_pct


        Where 20 is the percentage of maximum performance you want to allow. Setting this to 10% will probably result in extremely sluggish GUI, but you can try and see.



        Sources: kernel.org





        share













        Your system is probably using intel_pstate driver.



        Setting this driver's governor is very easy. To set all CPUs to maximum frequency, just use the following command:



        echo 100 | sudo tee /sys/devices/system/cpu/intel_pstate/min_perf_pct


        To do the opposite, and force low power on the CPUs, issue:



        echo 20 | sudo tee /sys/devices/system/cpu/intel_pstate/max_perf_pct


        Where 20 is the percentage of maximum performance you want to allow. Setting this to 10% will probably result in extremely sluggish GUI, but you can try and see.



        Sources: kernel.org






        share











        share


        share










        answered 6 mins ago









        chronos00chronos00

        339314




        339314






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f916382%2fubuntu-get-actual-current-cpu-clock-speed%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

            Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

            Should I use Docker or LXD?How to cache (more) data on SSD/RAM to avoid spin up?Unable to get Windows File...