You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: MultiTierDataMovement.md
+3-25Lines changed: 3 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ thread (green) is integrated to the CacheLib architecture.
12
12
13
13
## Synchronous Eviction and Promotion
14
14
15
-
-`disableEvictionToMemory`: Disables eviction to memory (item is always evicted to NVMe or removed
15
+
-`disableEviction`: Disables eviction to memory (item is always evicted to NVMe or removed
16
16
on eviction)
17
17
18
18
## Background Evictors
@@ -23,7 +23,7 @@ strategies and general parameters.
23
23
24
24
-`backgroundEvictorIntervalMilSec`: The interval that this thread runs for - by default
25
25
the background evictor threads will wake up every 10 ms to scan the AllocationClasses. Also,
26
-
the background evictor thead will be woken up everytime there is a failed allocation (from
26
+
the background evictor thread will be woken up everytime there is a failed allocation (from
27
27
a request handling thread) and the current percentage of free memory for the
28
28
AllocationClass is lower than `lowEvictionAcWatermark`. This may render the interval parameter
29
29
not as important when there are many allocations occuring from request handling threads.
@@ -59,7 +59,7 @@ don't set this above `10`.
59
59
60
60
## Background Promoters
61
61
62
-
The background promotes scan each class to see if there are objects to move to a lower
62
+
The background promoters scan each class to see if there are objects to move to a lower
63
63
tier using a given strategy. Here we document the parameters for the different
64
64
strategies and general parameters.
65
65
@@ -93,25 +93,3 @@ This value should correlate with `lowEvictionAcWatermark`, `highEvictionAcWaterm
93
93
-`maxPromotionBatch`: The number of objects to promote in batch during BG promotion. Analogous to
94
94
`maxEvictionBatch`. It's value should be lower to decrease contention on hot items.
95
95
96
-
## Allocation policies
97
-
98
-
-`maxAcAllocationWatermark`: Item is always allocated in topmost tier if at least this
99
-
percentage of the AllocationClass is free.
100
-
-`minAcAllocationWatermark`: Item is always allocated in bottom tier if only this percent
101
-
of the AllocationClass is free. If percentage of free AllocationClasses is between `maxAcAllocationWatermark`
102
-
and `minAcAllocationWatermark`: then extra checks (described below) are performed to decide where to put the element.
103
-
104
-
By default, allocation will always be performed from the upper tier.
105
-
106
-
-`acTopTierEvictionWatermark`: If there is less that this percent of free memory in topmost tier, cachelib will attempt to evict from top tier. This option takes precedence before allocationWatermarks.
107
-
108
-
### Extra policies (used only when percentage of free AllocationClasses is between `maxAcAllocationWatermark`
109
-
and `minAcAllocationWatermark`)
110
-
-`sizeThresholdPolicy`: If item is smaller than this value, always allocate it in upper tier.
111
-
-`defaultTierChancePercentage`: Change (0-100%) of allocating item in top tier
112
-
113
-
## MMContainer options
114
-
115
-
-`lruInsertionPointSpec`: Can be set per tier when LRU2Q is used. Determines where new items are
116
-
inserted. 0 = insert to hot queue, 1 = insert to warm queue, 2 = insert to cold queue
117
-
-`markUsefulChance`: Per-tier, determines chance of moving item to the head of LRU on access
0 commit comments