From: Jens Axboe <jens.axboe@oracle.com>
To: Chris Worley <worleys@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Every 13 hours sees a spike in fio CPU consumption, and a drop in IOPS/throughput
Date: Sat, 31 Oct 2009 07:58:45 +0100 [thread overview]
Message-ID: <20091031065845.GV10727@kernel.dk> (raw)
In-Reply-To: <f3177b9e0910300949r62e057adqd966bca61174e035@mail.gmail.com>
On Fri, Oct 30 2009, Chris Worley wrote:
> On Fri, Oct 30, 2009 at 9:20 AM, Chris Worley <worleys@gmail.com> wrote:
> > I'm running fio benchmarks for 120 hours:
> >
> > fio --rw=randrw --bs=4k --rwmixread=60 --numjobs=64 --iodepth=64
> > --sync=0 --direct=1 --randrepeat=0 --ioengine=libaio
> > --filename=/dev/sde --filename=/dev/sdf --name=test --loops=10000
> > --size=322122547200 --runtime=432000 --group_reporting
> >
> > The fio threads are generally reporting 100K IOPS and each of the 64
> > fio threads uses less than 10% CPU.
> >
> > But, every 13 hours (nearly to the minute), for ~200 seconds, the FIO
> > threads start consuming large amounts of CPU, and the IOPS drop to
> > ~40K:
>
> Josh is brilliant:
>
> (322122547200[bytes per test]*64[threads])/(4096[block
> size]*100000[IOPS]*3600[seconds per hour])=13 hours
>
> ...it's restarting the next loop and recalculating the random maps
> every 13 hours
Awesome! It should just give it or re-clean the random map, that is
likely where the bug is. Looking forward to a tested patch :-)
--
Jens Axboe
prev parent reply other threads:[~2009-10-31 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 15:20 Every 13 hours sees a spike in fio CPU consumption, and a drop in IOPS/throughput Chris Worley
2009-10-30 16:49 ` Chris Worley
2009-10-31 6:58 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091031065845.GV10727@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=fio@vger.kernel.org \
--cc=worleys@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.