public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: avi@redhat.com, mtosatti@redhat.com
Cc: kvm@vger.kernel.org
Subject: [PATCH 0/3 kvm-unit-tests] Dirty logging performance test
Date: Sun, 15 Jan 2012 12:41:31 +0900	[thread overview]
Message-ID: <20120115124131.3b460d1d85194edaa251e635@gmail.com> (raw)

My 32 bit host running on an intel core i3 box said:

  $ ./api/dirty-log-perf
  dirty-log-perf: 262144 slot pages / 262144 mem pages
  rip 804a74a
  rip 804a74a
  get dirty log:      51571 ns for          1 dirty pages
  rip 804a74a
  get dirty log:      81190 ns for          2 dirty pages
  rip 804a74a
  get dirty log:      66606 ns for          4 dirty pages
  rip 804a74a
  get dirty log:      60408 ns for          8 dirty pages
  rip 804a74a
  get dirty log:      46711 ns for         16 dirty pages
  rip 804a74a
  get dirty log:      83563 ns for         32 dirty pages
  rip 804a74a
  get dirty log:      74367 ns for         64 dirty pages
  rip 804a74a
  get dirty log:      87240 ns for        128 dirty pages
  rip 804a74a
  get dirty log:     140161 ns for        256 dirty pages
  rip 804a74a
  get dirty log:     191288 ns for        512 dirty pages
  rip 804a74a
  get dirty log:     981045 ns for       1024 dirty pages
  rip 804a74a
  get dirty log:    1000755 ns for       2048 dirty pages
  rip 804a74a
  get dirty log:    1122837 ns for       4096 dirty pages
  rip 804a74a
  get dirty log:    1362598 ns for       8192 dirty pages
  rip 804a74a
  get dirty log:    1202789 ns for      16384 dirty pages
  rip 804a74a
  get dirty log:    1598484 ns for      32768 dirty pages
  rip 804a74a
  get dirty log:    2456946 ns for      65536 dirty pages
  rip 804a74a
  get dirty log:    3366358 ns for     131072 dirty pages
  rip 804a74a
  get dirty log:    5634134 ns for     262144 dirty pages

Takuya Yoshikawa (3):
  Add dirty logging performance test
  dirty-log-perf: Split guest memory into two slots
  dirty-log-perf: Take slot size from command line

 api/dirty-log-perf.cc |  144 +++++++++++++++++++++++++++++++++++++++++++++++++
 config-x86-common.mak |    5 ++-
 2 files changed, 148 insertions(+), 1 deletions(-)
 create mode 100644 api/dirty-log-perf.cc

-- 
1.7.5.4


             reply	other threads:[~2012-01-15  3:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15  3:41 Takuya Yoshikawa [this message]
2012-01-15  3:43 ` [PATCH v2 1/3 kvm-unit-tests] Add dirty logging performance test Takuya Yoshikawa
2012-01-15  3:44 ` [PATCH 2/3 kvm-unit-tests] dirty-log-perf: Split guest memory into two slots Takuya Yoshikawa
2012-01-15  3:45 ` [PATCH 3/3 kvm-unit-tests] dirty-log-perf: Take slot size from command line Takuya Yoshikawa
2012-01-18 13:50 ` [PATCH 0/3 kvm-unit-tests] Dirty logging performance test Marcelo Tosatti

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=20120115124131.3b460d1d85194edaa251e635@gmail.com \
    --to=takuya.yoshikawa@gmail.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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