49%
20.05.2014
Viewing Server Topology
01 # numactl --hardware
available: 8 nodes (0-7)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9
node 0 size: 16373 MB
node 0 free: 15837 MB
node 1 cpus: 10 11 12 13 14 15 16 17 18 19
node 1
49%
29.09.2020
, "Kubernetes k3s Lightweight Distro" [6], which discusses using the magically tiny K3s within Internet of Things (IoT) applications.
The name of K3s came from Kubernetes' often abbreviated form K8s; according
49%
13.12.2022
Packages:
(1/6): dhcp-common-4.3.6-47.el8.noarch.rpm 902 kB/s | 206 kB 00:00
(2/6): dhcp-libs-4.3.6-47.el8.x86_64.rpm 3.1 MB/s | 147 kB 00:00
(3/6
49%
07.10.2014
.snap
s ntestvm1.img 5 8.0 GB 292 MB 2.4 GB 2014-03-01 11:42 982a3a 2 mar.snap
s ntestvm1.img 6 8.0 GB 128 MB 2.6 GB 2014-03-10 19:48 982a3b 2 mar2.snap
ntestvm1.img 0 8.0 GB
49%
16.03.2021
.4MBps and random reads 1.9MBps. The good news is that whereas random writes dropped a tiny bit to 1.2MBps (Listing 6), random reads increased to almost double the throughput with a rate of 3.3MBps
49%
11.04.2016
(512 MB) copied, 49.1424 s, 10.4 MB/s
If you want to empty the read and write cache for benchmark purposes, you can do so using:
sync; echo 3 > /proc/sys/vm/drop_caches
Sequential access
48%
17.02.2015
5420 Octa
Quad ARM Cortex-A15 (32KB instruction/32KB data/2MB L2) @1.8GHz, Quad-core ARM Cortex-A7 (32KB/32KB/512KB) @1.3GHz
Mali T-628 MP6
3GB LPDDR3e RAM (14.9GBps memory
48%
25.02.2013
.00 0.00
01/31/2013 09:56:03 AM
avg-cpu: %user %nice %system %iowait %steal %idle
6.00 0.00 2.00 0.50 0.00 91.50
Device: rrqm/s wrqm/s r/s w/s rMB
48%
18.07.2013
mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
32 Cycle time: min=120ns recommended=120ns
33 PIO: pio0 pio1 pio2 pio3 pio4
34 Cycle time: no flow control=120
48%
30.11.2025
2
2
3
512KB < < 1MB
3
2
2
3
2
4
3
4
1MB < < 10MB
87
87
87
84
74
67
