From: Andrew Martin <amartin@xes-inc.com>
To: linux-bcache@vger.kernel.org
Subject: Performance testing with bcache
Date: Thu, 13 Mar 2014 15:12:16 -0500 (CDT) [thread overview]
Message-ID: <2000529324.55683.1394741536677.JavaMail.zimbra@xes-inc.com> (raw)
In-Reply-To: <155722734.53464.1394740311695.JavaMail.zimbra@xes-inc.com>
Hello,
I am working on setting up bcache on Ubuntu 13.10 (with kernel 3.11.0-17)
for read performance testing in writethrough mode. I've written a test script
which uses dd to write data to the bcache device, read it back in, and then
attempt to read it again (to measure cache speed):
# write the data to the disk
dd if=/dev/zero of=/path/to/bcache/mount/file.raw bs=512 count=2
# read the data (using iflag=nocache to make sure it gets into bcache's
# cache and doesn't use the kernel's cache)
dd if=/path/to/bcache/mount/file.raw of=/dev/null iflag=nocache
# now perform the read, which should read from bcache's cache
dd if=/path/to/bcache/mount/file.raw of=/dev/null iflag=nocache
However, if I cat /sys/block/bcache0/bcache/cache/cache_available_percent
before and after performing the read, the value is always 100. Would using
iflag=direct be better than iflag=nocache in this case? Is there a better
way to force data into the cache for this type of performance benchmarking?
Thanks,
Andrew Martin
next parent reply other threads:[~2014-03-13 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <155722734.53464.1394740311695.JavaMail.zimbra@xes-inc.com>
2014-03-13 20:12 ` Andrew Martin [this message]
2014-03-13 20:53 ` Performance testing with bcache Sitsofe Wheeler
2014-03-14 18:41 ` Andrew Martin
2014-03-14 21:16 ` Andrew Martin
2014-03-15 17:52 ` Sitsofe Wheeler
2014-04-04 17:06 ` Andrew Martin
2014-04-04 19:10 ` Kent Overstreet
2014-04-05 7:57 ` Sitsofe Wheeler
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=2000529324.55683.1394741536677.JavaMail.zimbra@xes-inc.com \
--to=amartin@xes-inc.com \
--cc=linux-bcache@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 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.