Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jeff Furlong <jeff.furlong@hgst.com>,
	Karl Cronburg <kcronbur@redhat.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: what is the sample logger doing when the buffer fills up?
Date: Thu, 7 Jul 2016 15:44:09 -0600	[thread overview]
Message-ID: <577ECD29.2090204@kernel.dk> (raw)
In-Reply-To: <BN3PR0401MB1457BF2D349098BBF7F579A2F73B0@BN3PR0401MB1457.namprd04.prod.outlook.com>

On 07/07/2016 03:04 PM, Jeff Furlong wrote:
> I am still seeing dropped entries on a slightly different case:
>
> # fio -version
> fio-2.12-5-g0b2e
>
> # fio --name=test_job --ioengine=libaio --direct=1 --rw=randread --iodepth=256 --size=100% --numjobs=2 --bs=4k --filename=/dev/nvme0n1 --group_reporting --write_bw_log=test_job --write_iops_log=test_job --write_lat_log=test_job --log_avg_msec=1000 --disable_lat=0 --disable_clat=0 --disable_slat=0 --runtime=60s --time_based --output=test_job
>
> # cat test_job_iops.1.log
> 1000, 375601, 0, 0
> 3000, 243539, 0, 0
> 4000, 462076, 0, 0

That's very odd. Is it just the 2000 that's dropped, or are there more?

-- 
Jens Axboe



  reply	other threads:[~2016-07-07 21:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 15:56 what is the sample logger doing when the buffer fills up? Karl Cronburg
2016-07-07 18:36 ` Jens Axboe
2016-07-07 19:46   ` Karl Cronburg
2016-07-07 21:04     ` Jeff Furlong
2016-07-07 21:44       ` Jens Axboe [this message]
2016-07-07 21:47         ` Jeff Furlong
2016-07-07 21:50           ` Jens Axboe
2016-07-18 18:24             ` Matthew Eaton
2016-07-19  0:09               ` Jeff Furlong
2016-07-20 20:29                 ` Karl Cronburg
2016-07-20 21:23                   ` Jeff Furlong
2016-07-20 21:28                     ` Jeff Furlong
2016-07-20 23:46                       ` Jens Axboe
2016-07-21 15:49                         ` Karl Cronburg
2016-07-21 17:00                           ` Jeff Furlong
2016-07-21 21:26                             ` Karl Cronburg
2016-07-21 23:26                               ` Jeff Furlong
2016-07-22 14:47                                 ` Jens Axboe
2016-07-22 15:55                                   ` Jens Axboe
2016-07-22 18:37                                     ` Jens Axboe
2016-07-22 18:52                                       ` Jeff Furlong
2016-07-22 18:55                                         ` Jens Axboe
2016-07-22 19:20                                           ` Jens Axboe
2016-07-22 19:40                                             ` Jeff Furlong
2016-07-22 19:49                                               ` Jens Axboe

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=577ECD29.2090204@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=jeff.furlong@hgst.com \
    --cc=kcronbur@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox