11%
02.08.2021
) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=32
fio-3.16
Starting 1 process
test: (groupid=0, jobs=1): err= 0: pid=12936: Sat Jun 19 14:48:48 2021
write: IOPS=250k, BW=977MiB/s (1024MB/s)(500
11%
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
11%
12.03.2013
is shown in Listing 1.
Listing 1: Sample nfsiostat Output
Linux 2.6.18-308.16.1.el5.centos.plus (home8) 02/10/2013 _i686_ (1 CPU)
02/10/2013 03:38:48 PM
Filesystem: rMB_nor/s wMB
11%
11.02.2016
amount of available RAM: 117,080MB in this case.
Mem used
: Amount of RAM used by the applications: 48,810MB in this case.
Mem free
: Potentially free RAM: 68,270MB in this case.
Mem cached
: RAM
11%
04.08.2011
guests, including an official certificate via the Microsoft Server Virtualization Validated Program (SVVP) for Intel and AMD processors. On the hardware front, XenServer supports up to 256GB RAM, 64 cores
11%
03.02.2022
] device to store /var/log, offloading the primary source of boot-time writes from the physical device to a 50MB RAM drive.
Figure 3: Three zram partitions
11%
05.08.2024
/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/bin/ansible
python version = 3.11.2 (main, Feb 17 2023, 09:48:02) [GCC 8.5.0 20210514 (Red Hat 8.5.0-18)] (/usr/bin/python3.11)
jinja version = 3.1.2
libyaml = False
11%
07.11.2023
5.3M 8.2k 5.3M 1% /run/lock
/dev/nvme1n1p1 1.1T 488G 468G 52% /home
/dev/nvme0n1p1 536M 6.4M 530M 2% /boot/efi
/dev/sda1 6.0T 3.4T 2.4T 60% /home2
tmpfs
11%
03.02.2022
(Figure 3).
Figure 3: Encrypting the device.
Instead of the -RecoveryKeyPath parameter, you can, among other things, specify the path to a recovery key
11%
27.08.2014
record size, (2) sequential read testing with 1MB record size, and (3) random write and read (4KB). In running these tests, I wanted to see what block layer information ioprof revealed.
The system I
