From: Mark Nelson <mark.nelson@dreamhost.com>
To: Tommi Virtanen <tommi.virtanen@dreamhost.com>
Cc: Samuel Just <sam.just@dreamhost.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: ioreplay allows replaying fs traces from a strace log file
Date: Thu, 12 Apr 2012 16:53:32 -0500 [thread overview]
Message-ID: <4F874EDC.7030409@dreamhost.com> (raw)
In-Reply-To: <CAORUGqAPAnC6fJZgvZhbwHY6VNQa3+T8DRBBfiRwBmf4kBRCyw@mail.gmail.com>
I played around with this about a month back during a rados bench run,
but had some trouble getting it to work when strace was attached to an
already running process. I didn't end up spending a lot of time on it
though. Jeff Layton also wrote a strace analyzer tool specifically for
IO, but it needs a bit of work to support -f. His stuff can be found here:
http://clusterbuffer.wetpaint.com/page/Strace+Analyzer
Mark
On 4/12/12 3:47 PM, Tommi Virtanen wrote:
> This looks interesting: http://code.google.com/p/ioapps/
next prev parent reply other threads:[~2012-04-12 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 20:47 ioreplay allows replaying fs traces from a strace log file Tommi Virtanen
2012-04-12 21:53 ` Mark Nelson [this message]
2012-05-12 9:31 ` Jiri Horky
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=4F874EDC.7030409@dreamhost.com \
--to=mark.nelson@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sam.just@dreamhost.com \
--cc=tommi.virtanen@dreamhost.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