16%
30.01.2020
.1989| 3.69449e-06| 3.12%| for j in range(0, p_num):
145| 12750000| 47.4793| 3.72387e-06| 3.14%| if (i != j):
146| 0| 0| 0| 0.00%|
147
16%
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
16%
21.01.2021
.86–2.66GHz
Jan 2010
Nehalem
Dual-core; 32+32 L1, 256KB L2, 3MB L3; 2.8GHz, two threads per core
Table 2: Supercomputer Processor Progression
Date
Processor
16%
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
16%
05.08.2024
the row- and column-major access patterns, but only with a small array.
In the next experiment, I'll update the size variable to 10,000 as the sole change, to obtain Listings 3 and 4. The array now
16%
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
16%
30.11.2025
53
47
44
439
128KB < < 256KB
0
2
0
0
0
0
0
2
256KB < < 512KB
2
2
2
3
2
16%
26.02.2014
reqs merged: 3.76/s Write reqs completed: 2.12/s
Read BW: 0.01 MB/s Write BW: 0.02 MB/s
Avg sector size issued 25.28 Avg
16%
04.12.2013
3 type rec
4 integer :: x, y, z
5 real :: value
6 end type rec
7
8 integer :: counter
9 integer :: counter_limit
10 integer :: ierr
11
12 type (rec) :: my
16%
30.11.2025
XPS13 laptop: 13.3-inch screen with edge-to-edge glass (1366x768 resolution), i7 2GHz Intel Core2 Duo processor, 4GB of RAM, and 256GB SSD, all in a 0.88x12.56x9.3-inch device weighing 2.99 pounds
