All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Kudryavtsev, Andrey O" <andrey.o.kudryavtsev@intel.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: REPORT: High CPU utilization since 2.2.5
Date: Wed, 25 Feb 2015 13:48:53 -0700	[thread overview]
Message-ID: <54EE3535.8060606@kernel.dk> (raw)
In-Reply-To: <D10CFEF2.19AB0%andrey.o.kudryavtsev@intel.com>

On 02/20/2015 04:10 PM, Kudryavtsev, Andrey O wrote:
> Hi Jens,
> I’m running NVMe SSD benchmarks which are using multi-job configurations in the most common scenarios.
> I have noticed that since 2.2.5 release FIO has 3-4 times higher CPU utilization on the same workload, same system, same kernel 3.18.
> In fact I’m not able to achieve 450k IOPS on latest Core-i7 CPU due to 100% utilization.
> I tracked down the changes back, 2.1.14 is the most stable for me. Release had 2.2.0 the reporting issues, which were fixed in 2.2.5 but introduced high CPU utilization instead.
> Did anyone notice that too?
> 
> Configuration details are bellow:
> 
> [global]
> name=4k random read 4 ios in the queue in 32 queues
> filename=/dev/nvme0n1
> ioengine=libaio
> direct=1
> bs=4k
> rw=randread
> iodepth=4
> numjobs=32
> buffered=0
> size=100%
> runtime=0
> randrepeat=0
> norandommap
> refill_buffers
> [job1]

Can you try and bisect the issue?

-- 
Jens Axboe



      parent reply	other threads:[~2015-02-25 20:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 23:10 REPORT: High CPU utilization since 2.2.5 Kudryavtsev, Andrey O
2015-02-21  9:20 ` Sitsofe Wheeler
2015-03-09 22:07   ` Kudryavtsev, Andrey O
2015-03-17 16:16     ` Jens Axboe
2015-03-18 12:33       ` Kudryavtsev, Andrey O
2015-02-21 15:18 ` Andrey Kuzmin
2015-02-25 20:48 ` 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=54EE3535.8060606@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=andrey.o.kudryavtsev@intel.com \
    --cc=fio@vger.kernel.org \
    /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.