Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
9223372036854775807
Description
The LDLM LRU algorithm is sub-optimal for managing locks on the client, since it can flush often-used locks when there are a large number of files accessed in a short time (e.g. filesystem scanning). It would be better to implement a more sophisticated cache mechanism, such as ARC, LFRU, or similar (see https://en.wikipedia.org/wiki/Cache_replacement_policies) that includes a frequency count on the lock in addition to only the age of the lock. That will ensure that more important top-level locks are more likely to stay on the client instead of getting flushed.
Attachments
Issue Links
- is related to
-
LU-7266 Fix LDLM pool to make LRUR working properly
- Open
-
LU-10602 Add file heat support for Persistent Client Cache
- Open
-
LU-17329 Relaxed POSIX Consistency for Lustre
- Open
-
LU-17493 restore LDLM cancel on blocking callback
- Open
-
LU-14517 Decrease default lru_max_age value
- Resolved
- is related to
-
LU-6529 Server side lock limits to avoid unnecessary memory exhaustion
- Closed
-
LU-14221 Client hangs when using DoM with a fixed mdc lru_size
- Closed
-
LU-17428 reduce default value for lru_max_age to 300s
- Resolved