| 1 |
Examples of bitesize-nd.stp, the Linux SystemTap version. |
| 2 |
|
| 3 |
|
| 4 |
This shows size distributions for requested block I/O, by process name: |
| 5 |
|
| 6 |
# ./bitesize-nd.stp |
| 7 |
Tracing block I/O... Hit Ctrl-C to end. |
| 8 |
^C |
| 9 |
I/O size (bytes): |
| 10 |
|
| 11 |
process name: flush-202:1 |
| 12 |
value |-------------------------------------------------- count |
| 13 |
1024 | 0 |
| 14 |
2048 | 0 |
| 15 |
4096 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 33 |
| 16 |
8192 |@@@@@@@@@@@@@@@@ 16 |
| 17 |
16384 |@@@@@@@@@ 9 |
| 18 |
32768 |@@@@ 4 |
| 19 |
65536 |@@@ 3 |
| 20 |
131072 | 0 |
| 21 |
262144 | 0 |
| 22 |
|
| 23 |
process name: kjournald |
| 24 |
value |-------------------------------------------------- count |
| 25 |
1024 | 0 |
| 26 |
2048 | 0 |
| 27 |
4096 |@ 4 |
| 28 |
8192 | 2 |
| 29 |
16384 | 2 |
| 30 |
32768 |@ 7 |
| 31 |
65536 |@ 5 |
| 32 |
131072 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 182 |
| 33 |
262144 | 0 |
| 34 |
524288 | 0 |
| 35 |
|
| 36 |
process name: randread.pl |
| 37 |
value |-------------------------------------------------- count |
| 38 |
1024 | 0 |
| 39 |
2048 | 0 |
| 40 |
4096 | 4 |
| 41 |
8192 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 1859 |
| 42 |
16384 | 0 |
| 43 |
32768 | 5 |
| 44 |
65536 | 18 |
| 45 |
131072 | 0 |
| 46 |
262144 | 0 |
| 47 |
|
| 48 |
process name: tar |
| 49 |
value |-------------------------------------------------- count |
| 50 |
1024 | 0 |
| 51 |
2048 | 0 |
| 52 |
4096 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 1645 |
| 53 |
8192 |@@@@@@@@@@@@@@@@@@@@@@@@@ 836 |
| 54 |
16384 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 1394 |
| 55 |
32768 |@@@@@@@@@@@@@@@@ 532 |
| 56 |
65536 |@@@@@ 180 |
| 57 |
131072 |@@@@@@ 219 |
| 58 |
262144 | 0 |
| 59 |
524288 | 0 |
| 60 |
|
| 61 |
tar(1) was archiving a directory of varying sized files, and writing an output |
| 62 |
file, which creates the distribution seen above. |
| 63 |
|
| 64 |
The randread.pl program was performing 8 Kbyte random reads. Note that there |
| 65 |
were a few larger I/O: some custom SystemTap can be used to explain this. Eg, |
| 66 |
show kernel stack traces for I/O larger than 32 Kbytes. I'd guess it was |
| 67 |
file system metadata. |
| 68 |
|
| 69 |
The aim of this tool is to help characterize the disk I/O workload. |