100%
25.09.2023
Rubén Llorente ... is easy enough (superuser privileges are required):
arp -s 192.168.90.55 00:0c:29:c1:91:b1
The last field of the command is the MAC address, which is the unique identifier of the network device to which
31%
02.08.2021
.31 0.05
sdd 1.42 0.00 50.96 0.00 0.00 0.00 0.00 0.00 0.44 0.00 0.00 35.83 0.00 0.38 0.05
md0 12.43 12.17 54.39 48.68 0.00
31%
12.05.2021
.
Listing 6: iostat
Output
$ iostat -x -d 2 -c
Linux 5.4.12-050412-generic (dev-machine) 03/14/2021 _x86_64_ (4 CPU)
avg-cpu: %user %nice %system %iowait %steal %idle
0.79 0.07 1.19 2.89 0.00
28%
07.10.2014
/lib/sheepdog
root 582 581 0 13:13 ? 12:00:00 AM sheep -p 7000 /var/lib/sheepdog
# grep sheep /proc/mounts
/dev/sdb1 /var/lib/sheepdog ext4 rw,relatime,data=ordered 0 0
# grep sheep /etc/fstab
/dev
27%
11.02.2016
B/s wkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
sda 2.00 8.00 2.00 9500.00 16.00 151948.00 31.99 1.07 0.11 4.00 0.11 0.09 88.40
If your read or write
26%
12.09.2013
');
burncpu
-----------------
00:00:30.000053
The results take 30 seconds to deliver. The CPU load table shows the associated database process for this time (Figure 1).
Listing 1
burncpu
01
26%
20.02.2012
.57, 0.00, 12.76, 85, 0
2012-01-09 21:09:21, 84, 4.84, 0, 0.29, 17.36, 0.00, 5.09, 90, 0
2012-01-09 21:09:47, 80, 4
26%
19.11.2019
Jobs: 1 (f=1): [w(1)][100.0%][w=654MiB/s][w=167k IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=1225: Sat Oct 12 19:20:18 2019
write: IOPS=168k, BW=655MiB/s (687MB/s)(10.0GiB/15634msec); 0
25%
18.07.2013
buffered disk reads: 616 MB in
3.00 seconds = 205.03 MB/sec
$ hdparm -T /dev/sda
/dev/sda:
Timing cached reads: 6292 MB in
2.00 seconds = 3153.09 MB/sec
If this were a spinning disk, you would also
25%
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
