Re: Metadata vs UserData caching in BlueStore

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 12/15/2016 11:24 AM, Igor Fedotov wrote:
Sage et al,

shouldn't we have bluestore_cache_metadata_ratio set to 1 by default? To
concentrate on metadata caching..

I would contend that it should be high (we've already bumped it up, I'd go higher still), but isn't 1 a little excessive? Ultimately this should all be automatic based on heuristics imho.


IMHO Onode caching is much more important and profitable than user data
one. It's rather a client misbehavior to cause cache hit when accessing
user data but it's  highly expected for onode metadata.

We should take care not to run into the same problem the kernel does. With too many cached entries things can get slow. It's another trade-off we need to watch out for. There may need to be a (hopefully automatically generated) soft limit, and potentially a hard limit.


Moreover user data caching is probably already exists at block device
level hence we rather duplicate disk cache....

What do you think?

Thanks,

Igor

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux