18%
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
18%
30.11.2020
: Pull complete
3db6272dcbfa: Pull complete
Digest: sha256:8be26f81ffea54106bae012c6f349df70f4d5e7e2ec01b143c46e2c03b9e551d
Status: Downloaded newer image for registry:2
docker.io/library/registry:2
17%
30.01.2020
without profiling).
Listing 3
pprofile Output
Command line: md_002.py
Total duration: 1662.48s
File: md_002.py
File duration: 1661.74s (99.96%)
Line #| Hits| Time| Time per hit
17%
18.06.2014
]: 13502 ( 3.48%) ( 87.59% cumulative)
[ 64- 128 KB]: 12083 ( 3.11%) ( 90.70% cumulative)
[ 128- 256 KB]: 8623 ( 2.22%) ( 92.93% cumulative)
[ 256- 512 KB]: 13437 ( 3
17%
09.12.2019
in execution time by about a factor of 10 (i.e., it ran 10 times slower than without profiling).
Listing 3: pprofile
Output
Command line: md_002.py
Total duration: 1662.48s
File: md_002.py
File duration: 1661
17%
25.03.2020
7 1 56008 loop1
06 7 2 56184 loop2
07 7 3 91264 loop3
08 259 0 244198584 nvme0n1
09 8 0 488386584 sda
10 8 1 1024 sda1
11
17%
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
17%
21.01.2020
7 1 56008 loop1
06 7 2 56184 loop2
07 7 3 91264 loop3
08 259 0 244198584 nvme0n1
09 8 0 488386584 sda
10 8 1 1024 sda1
11
16%
30.01.2024
Dell Precision Workstation T7910
Power
1,300W
CPU
2x Intel Xeon Gold E5-2699 V4, 22 cores, 2.4GHz, 55MB of cache, LGA 2011-3
GPU, NPU
n/a*
Memory
16%
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
