mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>,
	Anna Schumaker <Anna.Schumaker@netapp.com>,
	Sagi Grimberg <sagi@grimberg.me>, <linux-nfs@vger.kernel.org>,
	<ying.huang@intel.com>, <feng.tang@intel.com>,
	<fengwei.yin@intel.com>, <oliver.sang@intel.com>
Subject: Re: [linus:master] [nfs]  49b29a573d:  filebench.sum_operations/s -85.6% regression
Date: Tue, 13 Aug 2024 14:59:52 +0800	[thread overview]
Message-ID: <ZrsEaIEbjpT80P9/@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20240813064955.GA14163@lst.de>

hi,  Christoph Hellwig,

On Tue, Aug 13, 2024 at 08:49:55AM +0200, Christoph Hellwig wrote:
> On Tue, Aug 13, 2024 at 02:47:48PM +0800, Oliver Sang wrote:
> > no in our tests, becomes even worse actually. detail data is in [1]
> 
> Thanks.  Do you have a good summary of what operations this counts?

sorry I don't have many details. not sure if https://github.com/filebench/filebench/wiki
is helpful for you?

and a raw data run by this test looks like below

2024-08-13 02:24:56 filebench -f /lkp/benchmarks/filebench/share/filebench/workloads/randomrw.f
Filebench Version 1.5-alpha3
0.000: Allocated 177MB of shared memory
0.001: Random RW Version 3.0 personality successfully loaded
0.001: Populating and pre-allocating filesets
0.001: Removing largefile1 tree (if exists)
0.002: Pre-allocating directories in largefile1 tree
0.119: Pre-allocating files in largefile1 tree
49.469: Waiting for pre-allocation to finish (in case of a parallel pre-allocation)
49.469: Population and pre-allocation of filesets completed
49.469: Starting 1 rand-rw instances
50.472: Running...
110.478: Run took 60 seconds...
110.478: Per-Operation Breakdown
rand-write1          11769ops      196ops/s   1.5mb/s    5.096ms/op [0.002ms - 1567.054ms]
rand-read1           49402ops      823ops/s   6.4mb/s    1.214ms/op [0.001ms - 1567.058ms]
110.478: IO Summary: 61171 ops 1019.414 ops/s 823/196 rd/wr   8.0mb/s 1.961ms/op
110.478: Shutting down processes
2024-08-13 02:26:48 sleep 100
/nfs/sdd1/largefile1
/nfs/sdd1/lost+found
/nfs/sdd1/wait_for_nfs_grace_period
2024-08-13 02:28:28 rm -rf /nfs/sdd1/largefile1 /nfs/sdd1/lost+found /nfs/sdd1/wait_for_nfs_grace_period


our bot parse it as:

{
  "filebench.sum_operations": [
    61171
  ],
  "filebench.sum_operations/s": [
    1019.414
  ],
  "filebench.sum_reads/s": [
    823
  ],
  "filebench.sum_writes/s": [
    196
  ],
  "filebench.sum_bytes_mb/s": [
    8.0
  ],
  "filebench.sum_time_ms/op": [
    1.961
  ]
}

  reply	other threads:[~2024-08-13  7:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08  7:35 kernel test robot
2024-08-12 11:21 ` Christoph Hellwig
2024-08-13  6:47   ` Oliver Sang
2024-08-13  6:49     ` Christoph Hellwig
2024-08-13  6:59       ` Oliver Sang [this message]
2024-08-14 13:04         ` Christoph Hellwig
2024-08-16  2:11           ` Oliver Sang

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=ZrsEaIEbjpT80P9/@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=sagi@grimberg.me \
    --cc=ying.huang@intel.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

all inboxes | Powered by JetHome®