15%
05.08.2024
.io/library/ubuntu latest 35a88802559d 7 weeks ago 80.6 MB
docker.io/library/hello-world latest d2c94e258dcb 15 months ago 28.5 kB
Listing 12: Checking for GFortran
$ podman run -it ubuntu-dev2 /bin/bash
root
15%
19.02.2013
10 ipv6 nd suppress-ra
11 !
12 interface eth1
13 ip address 10.55.55.1/24
14 ipv6 nd suppress-ra
Figure 1: The sample network consists of two
15%
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
15%
12.05.2021
_age Always - 400
10 Spin_Retry_Count 0x0013 100 099 --- Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 --- Old_age Always - 135
184 End
15%
30.01.2020
]
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 zone resets
[ ... ]
Run status group 0 (all jobs):
WRITE: bw=655Mi
15%
30.11.2025
creates a 256MB file in the current directory along with process for the job. This process reads complete file content in random order. Fio records the areas that have already been read and reads each area
15%
18.07.2013
D revision 1
10 Supported: 7 6 5 4
11 Configuration:
12 Logical max current
13 cylinders 16383 16383
14 heads 16 16
15
15%
04.04.2023
devices and compared the resulting write performance. Today, I am examining the limits of SD performance in a specific SBC instead: the all-in-one Raspberry Pi 400. (Figure 1). The Raspberry Pi 400 [2
15%
30.11.2025
of read requests issued to the device per second.
w/s
: Number of write requests issued to the device per second.
rMB/s
: Number of megabytes read from the device per second.
wMB/s
: Number
15%
30.11.2025
were run on a virtual system (using ESX as the hypervisor) with fixed reservations for CPU and memory. To be more precise, I used a virtual CPU running at 1.5GHz and with 512MB of RAM in the virtual
