Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-2126

test use of madvise to improve performance of the replication oplog

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Minor - P4 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.

      http://linux.die.net/man/2/madvise

            Assignee:
            Unassigned Unassigned
            Reporter:
            dwight@mongodb.com Dwight Merriman
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: