| W. Norcott. IOzone benchmark source code, version 2.01, 1994. |
....is explained in more detail in 2.2.4. 2.2.3 File system As mentioned above, each VServer is given its own file system, and files belonging to di#erent Virtual Servers are not accessible. In that sense, the potential processing overhead needed to provide this isolation has to be measured. IOzone [12] is a filesystem benchmark tool, which generates and measures a variety of file operations. The IOzone benchmark was used to measure the file system throughput in read, write, random read and random write operations. Again, I compared the performance of accessing the file system both inside ....
W. Norcott. IOzone benchmark source code, version 2.01, 1994.
....The few file system benchmarks that do exist are designed to test workstation class file systems, both standalone and in a networked environment. Several of the benchmarks consist of a single program sending many read and write requests to the file system; such programs include IOStone [1] iozone [4], and bonnie [5] These benchmarks are designed to gauge the maximum file system or disk system performance available to a single application over a short period of time. However, constant improvements in memory size and disk performance require scalable benchmarks; Chen s scalable disk benchmark ....
W. Norcott, IOzone benchmark source code, version 2.01, posted to comp.sources.misc, October 30, 1994. Available from ftp://www.cs.umbc.edu/pub/elm/iobenchmarks/iozone01.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC