24%
07.01.2014
.
[laytonjb@home4 TEST]$ du -sh backup.0
14M backup.0
[laytonjb@home4 TEST]$ du -sh backup.1
12M backup.1
[laytonjb@home4 TEST]$ du -sh backup.2
9.2M backup.2
[laytonjb@home4 TEST]$ du -sh backup.3
7.7M backup
24%
07.10.2014
. The second number is percent CPU load from the system (0.3%sy), and the next is percentage of jobs that are "nice" [2] (0.0%ni). After that, Top lists percent overall CPU time idle (86.3%id; four real cores
24%
19.11.2019
, ioengine=libaio, iodepth=32
fio-3.1
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][r=0KiB/s,w=1401KiB/s][r=0,w=350 IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=3104: Sat Oct 12 14:39:08 2019
write: IOPS=352
24%
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
23%
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
23%
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
23%
29.09.2020
sitting at less than 50MB (and using less than half the RAM of a standard cluster) the binary that runs K3s is a sight to behold and well worth getting your hands on. Especially when it's deemed production
23%
25.03.2020
] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sdd1[5] sde1[4] sdc1[2] sdb1[1] nvme0n1p1[0](J)
20508171264 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [UU
23%
21.01.2020
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
Next, verify that the RAID configuration has been created (Listing 3). You will immediately notice that the array initializes
23%
17.02.2015
Xino-Lime
Linux
All-winner A10 processor
Single ARM Cortex-A8 @1GHz
Mali-400
512MB DDR3
SATA connector, 2 USB, Fast Ethernet, USB OTG, HDMI
1.9W
$44/EUR 30
