kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: lmr@redhat.com, autotest@test.kernel.org
Cc: kvm@vger.kernel.org
Subject: [Autotest PATCH v2 0/4] Network performance regression
Date: Thu, 05 Jan 2012 11:05:47 +0800	[thread overview]
Message-ID: <20120105030456.8563.65512.stgit@dhcp-8-167.nay.redhat.com> (raw)
In-Reply-To: <20111223102308.29662.59520.stgit@dhcp-8-167.nay.redhat.com>

This patchset adds a new network perf testcase for Windows,
refactors old netperf test, and support numa resource control.
Process the raw results to a 'standard format' at the end of test,
then we can analyze them with general module, compute average
and compare with old results.
User can configure test time/repeat times for getting stable results.

Welcome to give feedback, thanks in advance!

Changes from v1:
- refactor analysis module
- add new features in analysis code
- shape those two tests
- fix some script bugs
- add autoio script for ntttcp test

---

Amos Kong (4):
      virt-test: add NTttcp subtests
      virt-test: Refactor netperf test and add analysis module
      netperf: pin guest vcpus/memory/vhost thread to numa node
      virt: Introduce regression testing infrastructure


 client/tests/kvm/control        |    7 +
 client/tests/kvm/perf.conf      |   23 +++
 client/virt/scripts/ntttcp.au3  |   41 +++++
 client/virt/subtests.cfg.sample |   59 ++++++-
 client/virt/tests/analyzer.py   |  172 ++++++++++++++++++++++
 client/virt/tests/netperf.py    |  312 ++++++++++++++++++++++++++++-----------
 client/virt/tests/ntttcp.py     |  183 +++++++++++++++++++++++
 client/virt/tests/regression.py |   34 ++++
 8 files changed, 733 insertions(+), 98 deletions(-)
 create mode 100644 client/tests/kvm/perf.conf
 create mode 100755 client/virt/scripts/ntttcp.au3
 create mode 100644 client/virt/tests/analyzer.py
 create mode 100644 client/virt/tests/ntttcp.py
 create mode 100644 client/virt/tests/regression.py

-- 
Amos Kong

  parent reply	other threads:[~2012-01-05  3:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 10:28 [RFC PATCH 0/4] Network performance regression Amos Kong
2011-12-23 10:28 ` [RFC PATCH 1/4] virt-test: add NTttcp subtests Amos Kong
2011-12-23 10:28 ` [RFC PATCH 2/4] virt-test: Refactor netperf test and add analysis module Amos Kong
2011-12-23 10:28 ` [RFC PATCH 3/4] netperf: pin guest vcpus/memory/vhost thread to numa node Amos Kong
2011-12-23 10:28 ` [RFC PATCH 4/4] virt: Introduce regression testing infrastructure Amos Kong
2011-12-24  1:13   ` Yang Hamo Bai
2011-12-25  1:26     ` Amos Kong
2011-12-29 13:12 ` [RFC PATCH 0/4] Network performance regression Amos Kong
2012-01-05  3:05 ` Amos Kong [this message]
2012-01-05  3:05   ` [Autotest PATCH v2 1/4] virt-test: add NTttcp subtests Amos Kong
2012-01-05  3:06   ` [Autotest PATCH v2 2/4] virt-test: Refactor netperf test and add analysis module Amos Kong
2012-01-05  3:06   ` [Autotest PATCH v2 3/4] netperf: pin guest vcpus/memory/vhost thread to numa node Amos Kong
2012-01-05  3:06   ` [Autotest PATCH v2 4/4] virt: Introduce regression testing infrastructure Amos Kong
2012-01-06 20:17   ` [Autotest PATCH v2 0/4] Network performance regression Lucas Meneghel Rodrigues

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=20120105030456.8563.65512.stgit@dhcp-8-167.nay.redhat.com \
    --to=akong@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@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;
as well as URLs for NNTP newsgroup(s).