-
Type: Improvement
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
using madvise for local.oplog.rs (or log.oplog.$main) may improve performance, as we know the access pattern. for example this could save waste of the file system cache if the system knows in some cases it won't be needing the data again
specifically:
(1) MADV_SEQUENTIAL might perform better in general
(2) MADV_DONTNEED might make sense on a replica set non-primary. on a non-primary, no one is reading its oplog, we are just writing to it.
if these were tested and performance was the same, I would be in favor of using, as they probably make caching smarter, if anything.
- is duplicated by
-
SERVER-3509 madvise(DONT_NEED) portions of oplog all slaves have synced
- Closed
- related to
-
SERVER-9335 prefetch/fault-in the tail of the oplog in large chunks
- Closed