Tag: vdbench

Recently I found that vdbench was not giving me the amount of outstanding IO that I had intended to configure by using the “threads=N” parameter. It turned out that with Linux, most of the filesystems (ext2, ext3 and ext4) do not support concurrent directIO, although they do support directIO. This was a bit of a shock coming from Solaris which had concurrent directIO since 2001.

All the Linux filesystems I tested allow multiple outstanding IO’s if the IO is submitted using asynchronous IO (AKA asyncIO or AIO) but not when using multiple writer threads (except XFS). Unfortunately vdbench does not allow AIO since it tries to be platform agnostic.

fio however does allow either threads or AIO to be used and so that’s what I used in the experiments below.

The column fio QD is the amount of outstanding IO, or Queue Depth that is intended to be passed to the storage device. The column iostat QD is the actual Queue Depth seen by the device. The iostat QD is not “8” because the response time is so low that fio cannot issue the IO’s quickly enough to maintain the intended queue depth.

Device	fio QD	fio QD Type	direct	iostat QD	ps -efT | grep fio | wc -l
/dev/sd	8	libaio	Yes	7	5
/dev/sd	8	Threads	Yes	7	12
ext2 fs (mke2fs)	8	Threads	Yes	1	12
ext2 fs (mke2fs)	8	libaio	Yes	7	5
ext3 (mkfs -t ext3)	8	Threads	Yes	1	12
ext3 (mkfs -t ext3)	8	libaio	Yes	7	5
ext4 (mkfs -t ext4)	8	Threads	Yes	1	12
ext4 (mkfs -t ext4)	8	libaio	Yes	7	5
xfs (mkfs -t xfs)	8	Threads	Yes	7	12
xfs (mkfs -t xfs)	8	libaio	Yes	7	5

At any rate, all is not lost – using raw devices (/dev/sdX) will give concurrent directIO, as will XFS. These issues are well known by Linux DB guys, and I found interesting articles from Percona and Kevin Closson after I finally figured out what was going on with vdbench.

fio “scripts”

For the “threads” case.

For the “aio” case