From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests <fstests@vger.kernel.org>
Subject: Re: Any way to detect performance in a test case?
Date: Wed, 16 Jan 2019 12:47:21 +0800 [thread overview]
Message-ID: <643f7899-e010-2694-4af6-960f0fc6e5cc@gmx.com> (raw)
In-Reply-To: <20190116035745.GO4205@dastard>
[-- Attachment #1.1: Type: text/plain, Size: 1219 bytes --]
On 2019/1/16 上午11:57, Dave Chinner wrote:
> 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...
Sorry for the misunderstanding.
I mean if it's possible for a test case to just fail when hitting some
big performance regression.
E.g. one operation should finish in 30s, but when it takes over 300s,
it's definitely a big regression.
But considering how many different hardware/VM the test may be run on,
I'm not really confident if this is possible.
Thanks,
Qu
>
> Cheers,
>
> Dave.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-16 4:47 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
2019-01-16 4:47 ` Qu Wenruo [this message]
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=643f7899-e010-2694-4af6-960f0fc6e5cc@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=david@fromorbit.com \
--cc=fstests@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox