should cover, and how many such HitSets to store. Binning accesses
over time allows Ceph to independently determine whether an object was
accessed at least once and whether it was accessed more than once over
-some time period ("age" vs "temperature"). Note that the longer the
-period and the higher the count the more RAM will be consumed by the
-ceph-osd process. In particular, when the agent is active to flush or
-evict cache objects, all hit_set_count HitSets are loaded into RAM.
-
-Currently there is minimal benefit for hit_set_count > 1 since the
-agent does not yet act intelligently on that information.
+some time period ("age" vs "temperature").
The ``min_read_recency_for_promote`` defines how many HitSets to check for the
existence of an object when handling a read operation. The checking result is
ceph osd pool set {cachepool} min_read_recency_for_promote 1
+Note that the longer the ``hit_set_period`` and the higher the
+``min_read_recency_for_promote`` the more RAM will be consumed by the ceph-osd
+process. In particular, when the agent is active to flush or evict cache objects,
+all hit_set_count HitSets are loaded into RAM.
+
Cache mode
~~~~~~~~~~
ceph osd pool set {cachepool} min_read_recency_for_promote 1
-.. note:: The longer the period and the higher the count, the more RAM the
- ``ceph-osd`` daemon consumes. In particular, when the agent is active to
- flush or evict cache objects, all ``hit_set_count`` HitSets are loaded
- into RAM.
+.. note:: The longer the period and the higher the min_read_recency_for_promote,
+ the more RAM the ``ceph-osd`` daemon consumes. In particular, when the agent
+ is active to flush or evict cache objects, all ``hit_set_count`` HitSets are
+ loaded into RAM.
Cache Sizing