14%
25.01.2022
_GUI 184 results.tar.gz
20 cfq_tuning.tar.gz 1556 lvm_gui.tar.gz 4 runit.fdtree.bash
4 COLLECTL 4 LVM_VS_MD 4 SANDFORCE
4 CRYPT-2 20
14%
15.02.2012
rewinddir
0
0
0
0
0
0
0
0
fsync
21
21
21
21
21
22
26
31
lseekm
3
14%
26.01.2012
rewinddir
0
0
0
0
0
0
0
0
fsync
21
21
21
21
21
22
26
31
lseekm
3
14%
27.08.2014
provide useful information beyond how ioprof works. The benchmark I will use is IOzone.
IOzone Example
The ioprof test ran while I was running iozone three ways: (1) sequential write testing with 1MB
14%
02.02.2021
5221548db 58 seconds ago 5.67MB
80dc7d447a48 About a minute ago 167MB
alpine 3.9 78a2ce922f86 5 months ago 5.55MB
The command you really
14%
25.03.2021
6836191232 sdc
8 33 244197544 sdc1
8 48 6836191232 sdd
8 49 244197544 sdd1
Notice that I have one non-volatile memory express (NVMe) drive and two serial-attached SCSI (SAS
14%
14.09.2021
$(find /sys/devices/system/cpu -regex ".*cpu[0-9]+/topology/thread_siblings_list") | sort -n | uniq
0,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25
14%
03.02.2022
,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25,57
26,58
27,59
28,60
29,61
30,62
31,63
The lstopo tool
14%
11.04.2016
.40 0.00 0.54 1.66 0.00 96.39
Device: rrqm/s wrqm/s r/s w/s rMB/s wMB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
sda 393.19 2.17 137.48 2
14%
05.08.2024
spans 100 million elements, taking up 800MB of RAM – not at all an unusual size in any kind of numerical computing. This system is equipped with 8GB of RAM, so allocating the array itself is no trouble
