From: Nikolaus Rath <Nikolaus@rath.org>
To: linux-bcache@vger.kernel.org
Subject: Re: lvmcache performance
Date: Mon, 08 Feb 2016 14:05:24 -0800 [thread overview]
Message-ID: <87mvrarh7f.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <20160208091705.GA1612@rh-vpn> (Joe Thornber's message of "Mon, 8 Feb 2016 09:17:06 +0000")
On Feb 08 2016, Joe Thornber <thornber@redhat.com> wrote:
> On Sun, Feb 07, 2016 at 10:43:30AM -0800, Nikolaus Rath wrote:
>> Is that the wrong expectation? But even then, shouldn't I at least see
>> some improvement?
>
> Firstly, if you have the latest software, I suggest you switch to the
> smq cache policy which is generally out performing the old mq policy
> substantially.
Will try, thanks.
> Secondly, I think you may need to reset your expectations a bit.
> dm-cache is a slow moving cache. It monitors IO, detectings hotspots
> on the disk and then 'promotes' those regions to the SSD. You may
> find that the reads that occur during a boot, occur only infrequently
> once the system is booted.
Well, yes, but since in my case the cache is bigger than the origin,
shouldn't eventually *everything* end-up in the cache?
Is there a way to tell how often I need to access a block for it to be
promoted? I was hoping that the {read,write}_promote_adjustement
settings would actually cause promotion on the first access.
Best,
-Nikolaus
(No Cc on replies please, I'm reading the list)
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
prev parent reply other threads:[~2016-02-08 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 18:43 [linux-lvm] lvmcache performance Nikolaus Rath
2016-02-08 9:17 ` Joe Thornber
2016-02-08 16:51 ` John Stoffel
2016-02-08 22:05 ` Nikolaus Rath
2016-02-09 9:39 ` Mateusz Korniak
2016-02-08 22:05 ` Nikolaus Rath [this message]
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=87mvrarh7f.fsf@thinkpad.rath.org \
--to=nikolaus@rath.org \
--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.