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

Single-threaded journal compression becomes a bottleneck when using "durable" writes

    • Type: Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.4.3
    • Component/s: MMAPv1, Performance, Storage
    • None
    • Environment:
      Windows 7 Professional SP1 x64
    • Storage Execution

      When multiple threads save documents in "durable" fashion (I mean getLastError: 1, j: true) they all wait untill one thread running durThread() method persist these changes. Also this thread does compression, which becomes a bottleneck. More details are here https://jira.mongodb.org/browse/SERVER-9754?focusedCommentId=347003&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-347003

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            dnaumov Dmitry Naumov
            Votes:
            3 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: