« first day (3519 days earlier)      last day (1443 days later) » 

7:30 AM
Has anyone here ever used this feature?
 
8:01 AM
@Tim hah that’s quite amusing
 
 
3 hours later…
11:23 AM
is it possible for /proc/cpuinfo not to have the current CPU frequency in an Ubuntu system?
1
Q: How to acquire the current CPU frequency other than from `/proc/cpuinfo` or `/sys/devices/system/cpu/cpu*/cpufreq` under Linux

sunshilong369How can I get the current CPU frequency other than from /proc/cpuinfo or /sys/devices/system/cpu/cpu*/cpufreq on Linux (Ubuntu)? There is no /sys/devices/system/cpu/cpu*/cpufreq directory on my Ubuntu system. And there is no CPU MHz information in /proc/cpuinfo either. Could anybody give some ...

 
11:42 AM
@terdon on non-x86 yes, IIRC
@terdon here’s an Aarch64 system’s /proc/cpuinfo:
Processor       : AArch64 Processor rev 4 (aarch64)
processor       : 0
processor       : 1
processor       : 2
processor       : 3
Features        : fp asimd aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: AArch64
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4

Hardware        : sun50iw1p1
lscpu knows the min and max frequency but not the current frequency:
Architecture:          aarch64
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             4
CPU max MHz:           1344.0000
CPU min MHz:           480.0000
 
12:01 PM
@StephenKitt yeah, turns out the OP has ARM.
@StephenKitt makes sense. I think that just parses /proc/cpuinfo anyway.
 
@terdon it must get the min/max frequency somewhere else ...
 
 
1 hour later…
Tim
1:22 PM
(posted in meta)
 
298
A: Does Stack Exchange use caching and if so, how?

Kevin MontroseOh boy, have I been waiting for somebody to ask something like this. We really aggressively cache... basically everything. Virtually all pages accessed by (and subsequently served to) anonymous users are cached, whole cloth, via Output Caching. This isn't terribly interesting, but it is terrib...

 

« first day (3519 days earlier)      last day (1443 days later) »