73%
09.04.2019
in mv
ubuntu@aws:~/slow-mv$ strace -t mv 3GB.copy 3GB
19:00:09 execve("/bin/mv", ["mv", "3GB.copy", "3GB"], 0x7ffd0e7dddf8 /* 21 vars */) = 0
19:00:09 brk(NULL) = 0x55cd7d1ce000
72%
11.05.2021
.50GHz
Processor base frequency 2.5GHz
Max turbo frequency 4.5GHz
Cache 8MB
Four cores (eight with hyper-threading)
45W TDP
8GB DDR4-2933 memory
Maximum of two memory channels
72%
15.02.2012
.23%)
file_18591.pickle
3376.81946802
8.041807
(0.24%)
file_18592.pickle
3376.81726694
11.776699
(0.35%)
file_18593.pickle
3376
72%
26.01.2012
.23%)
file_18591.pickle
3376.81946802
8.041807
(0.24%)
file_18592.pickle
3376.81726694
11.776699
(0.35%)
file_18593.pickle
3376
72%
16.01.2013
-------------------------------------------------------------------------------
global - - - - - - -
master linux-x64 1 0.20 590.8M 68.1M 243.2M 0.0
node001 linux-x64 1 0
72%
06.10.2019
for later use. Whether the information is sold to interested customers or simply discarded is up to the operator of the DNS resolver. The DNS resolver from Google (8.8.8.8 and 8.8.4.4), for example, logs
72%
29.09.2020
/
version: ^2.2.0
- condition: fluent-bit.enabled
name: fluent-bit
repository: https://kubernetes-charts.storage.googleapis.com/
version: ^2.8.0
- condition: fluentd-elasticsearch.enabled
name
72%
21.01.2020
7 1 56008 loop1
06 7 2 56184 loop2
07 7 3 91264 loop3
08 259 0 244198584 nvme0n1
09 8 0 488386584 sda
10 8 1 1024 sda1
11 8
72%
30.01.2024
?
I already discussed BashTop in a previous issue [8], but today I shall focus on just one aspect of its CPU view: What happens when all those cores heat up? The system idles at 121W once booted up, so
72%
09.10.2017
: WARNING - Free memory per node close to zero.
Total Elapsed Time : 0d 0h 8m 40s 632ms
========================================================
Sampling Period : 10 seconds
Complete
