From: Mike Snitzer <snitzer@redhat.com>
To: CoolCold <coolthecold@gmail.com>
Cc: brice.barotin@gmail.com, linux-lvm@redhat.com
Subject: Re: [linux-lvm] dm-cache size is limited by 946GB
Date: Mon, 24 Jul 2017 12:07:20 -0400 [thread overview]
Message-ID: <20170724160720.GB19898@redhat.com> (raw)
In-Reply-To: <CAGqmV7oCXLyjio67mksc-rKrLQGvoyOeJfPH4T0or3STrbdbrA@mail.gmail.com>
On Sun, Jul 23 2017 at 9:48am -0400,
CoolCold <coolthecold@gmail.com> wrote:
> Hello!
> We started to adopting new servers for image storages, and hit the
> strange problem - no caching happens for cache lv > 946GB (so 947GB
> and above do no work).
>
> Storage box looks like:
> 2x240GB SSD for system (sw raid 1, lvm on top)
> 20x1.8TB SATA HDD for data (sw raid 10, md124 + lvm on top)
> 4x960GB SSD for dm-caching puprose (sw raid5, md125).
>
> Our naive approach was to create PV from md125 and make it all cache -
> around 2.6TB of cache for 16TB of "raw" data should be quite good.
> Cache created successfully, has seen the whole 2.6TB, but after
> copying ~ 3TB data from old box, we still got only misses for reads
> and writes in statistics and almost no activity in iostat for md125.
> When i say "almost no activity" it was having some write operations,
> but zeroes in KB -
> https://gist.github.com/CoolCold/f79bb706d4dd1c083a4f4ed0ebd850d5 -
> where dm-2 and dm-3 are cache data and cache meta volumes accordingly.
>
> We have "old" servers which are running a bit different setup in
> number of drives, they have 350-750GB of space for caching and it
> works well. We tried to reduce cache size for new box, it worked for
> 80GB, so bisected to 946GB.
>
> It doesn't look like any "magic" number (I though may be some problems
> around 2TB for signed/unsigned or so) and right now i'm out of ideas
> what the problem may be and need your advice.
>
> Kernel version we are using:
> 3.10.0-514.26.2.el7.x86_64
the 7.4 dm-cache will be much more performant than the 7.3 cache you
appear to be using.
As for you "no caching happens for cache lv > 946GB". Cache shouldn't
have any concerns about the size. It could be that your workload isn't
accessing the data enough to warrant promotion to the cache. dm-cache
is a "hotspot" cache. If you aren't accessing the data repeatedly then
you won't see much benefit (particularly with the 7.3 and earlier
releases).
Just to get a feel, you could try the latest upstream 4.12 kernel to see
how effective the 7.4 dm-cache will be for your setup.
Mike
next prev parent reply other threads:[~2017-07-24 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 13:48 [linux-lvm] dm-cache size is limited by 946GB CoolCold
2017-07-24 16:07 ` Mike Snitzer [this message]
2017-07-24 16:12 ` CoolCold
2017-07-25 11:46 ` 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=20170724160720.GB19898@redhat.com \
--to=snitzer@redhat.com \
--cc=brice.barotin@gmail.com \
--cc=coolthecold@gmail.com \
--cc=linux-lvm@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 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.