dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Nick Fisk <nick-ksME7r3P/wO1Qrn1Bg8BZw@public.gmane.org>,
	'Sage Weil' <sage-BnTBU8nroG7k1uMJSBkQmQ@public.gmane.org>
Cc: ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org,
	'device-mapper development'
	<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: Local SSD cache for ceph on each compute node.
Date: Tue, 29 Mar 2016 18:35:03 +0300	[thread overview]
Message-ID: <56FAA0A7.6050009@redhat.com> (raw)
In-Reply-To: <9be96412.9Ro.9Gf.hp.1e3JYGxgKk-ImYt9qTNe79BDgjK7y7TUQ@public.gmane.org>

On 03/29/2016 04:53 PM, Nick Fisk wrote:
>> -----Original Message-----
>> From: ceph-users [mailto:ceph-users-bounces-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org] On Behalf Of
>> Ric Wheeler
>> Sent: 29 March 2016 14:40
>> To: Nick Fisk <nick-ksME7r3P/wO1Qrn1Bg8BZw@public.gmane.org>; 'Sage Weil' <sage-BnTBU8nroG7k1uMJSBkQmQ@public.gmane.org>
>> Cc: ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org; device-mapper development <dm-
>> devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>> Subject: Re: [ceph-users] Local SSD cache for ceph on each compute node.
>>
>> On 03/29/2016 04:35 PM, Nick Fisk wrote:
>>> One thing I picked up on when looking at dm-cache for doing caching
>>> with RBD's is that it wasn't really designed to be used as a writeback
>>> cache for new writes, as in how you would expect a traditional
>>> writeback cache to work. It seems all the policies are designed around
>>> the idea that writes go to cache only if the block is already in the
>>> cache (through reads) or its hot enough to promote. Although there did
>>> seem to be some tunables to alter this behaviour, posts on the mailing
>>> list seemed to suggest this wasn't how it was designed to be used. I'm
>>> not sure if this has been addressed since I last looked at it though.
>>>
>>> Depending on if you are trying to accelerate all writes, or just your
> "hot"
>>> blocks, this may or may not matter. Even <1GB local caches can make a
>>> huge difference to sync writes.
>> Hi Nick,
>>
>> Some of the caching policies have changed recently as the team has looked
>> at different workloads.
>>
>> Happy to introduce you to them if you want to discuss offline or post
>> comments over on their list: device-mapper development <dm-
>> devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>>
>> thanks!
>>
>> Ric
> Hi Ric,
>
> Thanks for the heads up, just from a quick flick through I can see there are
> now separate read and write promotion thresholds, so I can see just from
> that it would be a lot more suitable for what I intended. I might try and
> find some time to give it another test.
>
> Nick

Let us know how it works out for you, I know that they are very interested in 
making sure things are useful :)

ric

  parent reply	other threads:[~2016-03-29 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <VI1PR05MB16772049FF17DD2D4DE93EDEE08A0@VI1PR05MB1677.eurprd05.prod.outlook.com>
     [not found] ` <1003879409.38672781.1458091493153.JavaMail.zimbra@redhat.com>
     [not found]   ` <VI1PR05MB1677B32D621D52ECFBD8C889E08A0@VI1PR05MB1677.eurprd05.prod.outlook.com>
     [not found]     ` <1517351774.38675790.1458092531934.JavaMail.zimbra@redhat.com>
     [not found]       ` <8C4FE234-AC6A-4F80-84DA-DCB69C58E874@ebay.com>
     [not found]         ` <VI1PR05MB1677291EA89E9C02BEE437C2E08A0@VI1PR05MB1677.eurprd05.prod.outlook.com>
     [not found]           ` <054DE45B-30E4-44B6-88CE-23FC207FE41E@ebay.com>
     [not found]             ` <56F792F6.9050400@redhat.com>
     [not found]               ` <DC9C5DB4-43C1-49DB-A37E-F7C6A9D3D172@ebay.com>
     [not found]                 ` <56FA46C9.6090500@redhat.com>
     [not found]                   ` <E5E25BC0-A526-4EB8-9EC0-80F6A7734B23@ebay.com>
     [not found]                     ` <56FA6792.1050005@redhat.com>
     [not found]                       ` <alpine.DEB.2.11.1603290827510.6473@cpach.fuggernut.com>
     [not found]                         ` <56FA7DEA.9010005@redhat.com>
     [not found]                           ` <ce98776b.9Ro.9Gf.cS.1kvo9AAN6V@mailjet.com>
     [not found]                             ` <ce98776b.9Ro.9Gf.cS.1kvo9AAN6V-ImYt9qTNe79BDgjK7y7TUQ@public.gmane.org>
2016-03-29 13:39                               ` Local SSD cache for ceph on each compute node Ric Wheeler
     [not found]                                 ` <56FA859B.5050608-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-29 13:53                                   ` Nick Fisk
2016-03-29 13:53                                 ` [ceph-users] " Nick Fisk
     [not found]                                 ` <9be96412.9Ro.9Gf.hp.1e3JYGxgKk@mailjet.com>
     [not found]                                   ` <9be96412.9Ro.9Gf.hp.1e3JYGxgKk-ImYt9qTNe79BDgjK7y7TUQ@public.gmane.org>
2016-03-29 15:35                                     ` Ric Wheeler [this message]
     [not found]                                       ` <56FAA0A7.6050009-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-30 13:02                                         ` Nick Fisk
2016-03-30 13:02                                       ` [ceph-users] " Nick Fisk

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=56FAA0A7.6050009@redhat.com \
    --to=rwheeler-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org \
    --cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=nick-ksME7r3P/wO1Qrn1Bg8BZw@public.gmane.org \
    --cc=sage-BnTBU8nroG7k1uMJSBkQmQ@public.gmane.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 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).