All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Hayakawa <ruby.wktk@gmail.com>
To: dm-devel@redhat.com
Cc: linux-kernel@vger.kernel.org, masami.hiramatsu@gmail.com,
	devel@etsukata.com
Subject: Re: dm-writeboost: Progress Report
Date: Fri, 23 May 2014 22:14:42 +0900	[thread overview]
Message-ID: <537F49C2.3000304@gmail.com> (raw)
In-Reply-To: <537775B0.2060907@gmail.com>

Hi Guys,

This progress report includes very important benchmarking results, which shows
i) Write will always improve - It boosts writes (396% in the best case) even with really small cache (say, 64MB) because of the sophisticated writeback optimization.
ii) Read won't be bad - It doesn't so much deteriorate the read (less than 1% for SSD+HDD case) because of the insignificant overhead.
iii) Good in application workloads - 22% improvement with read-intensive workload and 234-299% improvement with fileserver workload (using dbench)

Yeah, merging Writeboost into the mainline is my goal now and I really need your feedbacks.
For more details, please read the previous post.

Cheers,
- Akira

  reply	other threads:[~2014-05-23 13:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-17 14:44 dm-writeboost: Progress Report Akira Hayakawa
2014-05-23 13:14 ` Akira Hayakawa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-11  7:27 Akira Hayakawa
2014-01-13 10:09 ` Joe Thornber
2014-01-13 11:46   ` Akira Hayakawa
2014-01-13 15:14     ` Mike Snitzer
2014-01-13 21:03     ` Paul B. Henson
2014-01-19  1:16       ` Akira Hayakawa
2014-01-14 10:17     ` Joe Thornber
2013-11-04  5:17 Akira Hayakawa
2013-11-17 11:23 ` Akira Hayakawa

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=537F49C2.3000304@gmail.com \
    --to=ruby.wktk@gmail.com \
    --cc=devel@etsukata.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu@gmail.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.