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

Tailing the oplog requires paging in the recently added entries under WiredTiger

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.1
    • Component/s: WiredTiger
    • Labels:
    • Storage Execution
    • Fully Compatible
    • ALL

      While debugging a large performance drop related to the oplog filling (see SERVER-18079 for details) I noticed that the issue was exacerbated by the fact that the thread tailing the oplog is having to page in the recently added entries at the end of the oplog (see these stack traces from that ticket).

      Independent of the memory allocator issues on that ticket, it seems that having to page in the recently added oplog entries is not optimal for performance. Is there any way to avoid this?

            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            0 Vote for this issue
            13 Start watching this issue