I think to make pool-per-user (primary for cephfs; for security, quota, etc),
hundreds (or even more) of them. But I remember 2 facts:
1) info in manual about slowdown on many pools;
Yep, this is still a problem; pool-per-user isn't going to work well unless your users are covering truly prodigious amounts of space.
There is a new feature in raw RADOS that let you specify a separate "namespace" and set access capabilities based on those; it is being worked up through the rest of the stack now.
2) something in later changelog about hashed pool IDs (?).
This doesn't impact things one way or the other.
-Greg
How about now and numbers of pools?
And how to avoid serious overheads?
--
WBR, Dzianis Kahanovich AKA Denis Kaganovich, http://mahatma.bspu.unibel.by/
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
--
Software Engineer #42 @ http://inktank.com | http://ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
