mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Schöbel-Theuer" <thomas.schoebel-theuer@1und1.de>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Thomas Schöbel-Theuer" <Thomas.Schoebel-Theuer@1und1.de>
Subject: block level: new tool "blkreplay" for tests / benchmarking
Date: Wed, 23 May 2012 16:26:33 +0200	[thread overview]
Message-ID: <1337783193.1886.104.camel@tst0.s.schlund.de> (raw)

Hi all,

in some sense, blkreplay is just the opposite of the well-known kernel
tool blktrace: recordings of (natural) loads can be replayed in the
laboratory, measuring IO latencies (and other indicators) for later
visualization (so-called "sonar diagrams"), e.g. for comparison of IO
schedulers, or driver overhead, or network latencies, or hardware.

While blkreplay itself is a rather simple tool, the real value of the
GPL'ed blkreplay project might be the large collection of natural loads,
stemming from datacenters at 1&1.

The public collection of natural loads covers a broad range of
applications, such as databases (even commercial ones like Oracle),
shared hosting, virtualized servers, etc. Some loads are even 24h
recordings. The collection will be enhanced during the next few days
(internally at 1&1, we have already more than 1000 blktrace recordings,
so our main problem is selecting the "interesting" ones, otherwise you
could be overwhelmed).

blkreplay comes with a comprehensive manual of already 57 pages, which
will be extended during the next weeks.

Introduction / Abstract: www.blkreplay.org or
https://github.com/schoebel/blkreplay/wiki

Manual:
https://github.com/schoebel/blkreplay/raw/master/doc/blkreplay.pdf

Source code: https://github.com/schoebel/blkreplay

Collection of loads: http://www.blkreplay.org/loads/

Enjoy,

Thomas



                 reply	other threads:[~2012-05-23 14:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1337783193.1886.104.camel@tst0.s.schlund.de \
    --to=thomas.schoebel-theuer@1und1.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®