On Feb 08 2016, Joe Thornber <thornber@xxxxxxxxxx> 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.«
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
