From: Heinz Mauelshagen <heinzm@redhat.com>
To: dm-devel@redhat.com
Subject: Re: dm-cache warming
Date: Mon, 29 Jul 2013 12:16:11 +0200 [thread overview]
Message-ID: <51F640EB.6050701@redhat.com> (raw)
In-Reply-To: <51F294A0.6080103@cozx.com>
Hi,
dm-cache is a hot-spot cache. Ie. you need multiple accesses to the same
block to get it promoted into the cache (depending on the policy plugin
btw).
If your patterns is one-time-only access type, it ain't warm the cache.
Heinz
On 07/26/2013 05:24 PM, Dave Pitts wrote:
> Hello:
>
> I've been trying to do some performance testing for a client and can't
> seem to get the dm-cache warmed. The values displayed in the "dmsetup
> status" command seem too low. I've been trying to use the "raw"
> devices setup for the cache and NOT use a file system or database.
> I've tried sequential writes/reads to the devices (ie. dd ) and
> dividing up the space to be tested and do I/O over a number of
> segments to try to break any sequential I/O tests. Any ideas as to
> what I may doing wrong? Do I need to randomize the I/O?
>
> System: RHEL 7.0 Alpha3, 3.9.7 kernel
>
> Thanks in advance..
>
next prev parent reply other threads:[~2013-07-29 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 15:24 dm-cache warming Dave Pitts
2013-07-29 10:16 ` Heinz Mauelshagen [this message]
2013-07-29 10:40 ` Joe Thornber
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=51F640EB.6050701@redhat.com \
--to=heinzm@redhat.com \
--cc=dm-devel@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;
as well as URLs for NNTP newsgroup(s).