From: Dave Chinner <david@fromorbit.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: fstests <fstests@vger.kernel.org>
Subject: Re: Any way to detect performance in a test case?
Date: Wed, 16 Jan 2019 14:57:45 +1100 [thread overview]
Message-ID: <20190116035745.GO4205@dastard> (raw)
In-Reply-To: <f5404232-3b9a-6bb6-9841-a2a56f314e51@gmx.com>
On Wed, Jan 16, 2019 at 09:59:40AM +0800, Qu Wenruo wrote:
> Hi,
>
> Is there any way to detect (huge) performance regression in a test case?
>
> By huge performance regression, I mean some operation takes from less
> than 10s to around 400s.
>
> There is existing runtime accounting, but we can't do it inside a test
> case (or can we?)
>
> So is there any way to detect huge performance regression in a test case?
Just run your normal performance monitoring tools while the test is
running to see what has changed. Is it IO, memory, CPU, lock
contention or somethign else that is the problem? pcp, strace, top,
iostat, perf, etc all work just fine for finding perf regressions
reported by test cases...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-01-16 3:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 1:59 Any way to detect performance in a test case? Qu Wenruo
2019-01-16 3:57 ` Dave Chinner [this message]
2019-01-16 4:47 ` Qu Wenruo
2019-01-16 17:33 ` Vijaychidambaram Velayudhan Pillai
2019-01-17 0:16 ` Dave Chinner
2019-01-17 1:30 ` Qu Wenruo
2019-01-17 2:25 ` Dave Chinner
2019-01-23 0:51 ` Qu Wenruo
2019-01-23 4:18 ` Dave Chinner
2019-01-23 5:08 ` Qu Wenruo
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=20190116035745.GO4205@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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