From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Jan Tulak <jtulak@redhat.com>, fstests@vger.kernel.org
Cc: Lukas Czerner <lczerner@redhat.com>
Subject: Re: Performance testing
Date: Wed, 17 Sep 2014 13:36:54 +0400 [thread overview]
Message-ID: <87iokmtwp5.fsf@openvz.org> (raw)
In-Reply-To: <1410943724.31777.31.camel@jtulak>
On Wed, 17 Sep 2014 10:48:44 +0200, Jan Tulak <jtulak@redhat.com> wrote:
> Hi,
>
> I have began to work on some set of performance tests. I think it would
> be useful to have some standard set, because as far as I know, there is
> just little of performance testing and every of the few tests someone
> does is unique. I want to propose my ideas before I start to really
> write it, to fix possible complications.
>
> Mixing performance with regressions tests wouldn't be a good idea, so I
> thought about creating another category on the main level of tests
> (something like xfstests/tests/performance). Or it would be better to
> put it into entirely new directory, like xfstests/performance?
>
> From the beginning there would be some basic test cases, like sync/async
> read and write. Hopefully more natural cases, like a database server
> would be added later. For the IO testing, I want to use FIO for the
> specific workflow and eventually iozone for the basic synthetic tests.
>
> What I'm not sure is how a comparison between different versions could
> be done, because I don't see any infrastructure within fstests for
> cross-version comparison. (What would it do with regression tests
> anyway...) So I wonder if it should be done in this set at all. So the
> set would only print the measured values. Some other tool (which can be
> also included, but is not directly part of the performance tests set)
> could then be used to compare and/or plot graphs.
>
> Comments and questions? :-)
This kind of functionality already implemented in autotest via perf keyval
http://autotest.readthedocs.org/en/latest/main/local/Keyval.html
test case may produce any numbers of keyvalues which will be
automatically stored to standard database for later comparison.
>
> Jan Tulak
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-17 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 8:48 Performance testing Jan Tulak
2014-09-17 9:36 ` Dmitry Monakhov [this message]
2014-09-25 15:08 ` Jan Tulak
2014-09-18 0:36 ` Dave Chinner
2014-09-25 15:03 ` Jan Tulak
2014-09-27 0:47 ` Dave Chinner
2014-09-29 16:07 ` Jan Tulak
2014-10-25 17:10 ` Jan Tulak
[not found] <467BE4C0.2020203@bull.net>
[not found] ` <1182541578.9939.3.camel@localhost.localdomain>
[not found] ` <467C99F5.6060603@clusterfs.com>
[not found] ` <1182755567.4067.1.camel@localhost.localdomain>
[not found] ` <467FE8A5.4030508@bull.net>
[not found] ` <467FEAF7.7060902@clusterfs.com>
[not found] ` <4680CE9B.1030602@bull.net>
2007-06-26 9:48 ` performance testing Valerie Clement
2007-06-26 10:36 ` Girish Shilamkar
2007-06-26 11:03 ` Valerie Clement
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=87iokmtwp5.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=fstests@vger.kernel.org \
--cc=jtulak@redhat.com \
--cc=lczerner@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 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.