Messages in this thread | | | Date | Thu, 8 Jun 2006 16:00:13 +0200 | From | Jens Axboe <> | Subject | Re: adaptive readahead overheads |
| |
On Thu, Jun 08 2006, Andi Kleen wrote: > Voluspa <lista1@comhem.se> writes: > > > On Thu, 8 Jun 2006 19:37:31 +0800 Fengguang Wu wrote: > > > I'd like to show some numbers on the pure software overheads come with > > > the adaptive readahead in daily operations. > > [...] > > > > > > # time find /usr -type f -exec md5sum {} \; >/dev/null > > > > > > ARA > > > > > > 406.00s user 325.16s system 97% cpu 12:28.17 total > > > > Just out of interest, all your figures show an almost maxed out CPU. > > It might be because qemu has a poor IO model (old IDE) that is quite > CPU intensive to drive.
qemu ide supports dma, so it's ok in that respect. It doesn't support async io for the host though, so all io ends up blocking waiting for io to complete at the host. I would not advocate using qemu for benching these things, it's just not (yet) well suited for io testing.
-- Jens Axboe
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |