Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13271

Investigate changes in SERVER-42697: Expose tcmalloc_release_rate via setParameter

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.3, 4.2.3, 3.6.18, 4.0.18
    • Component/s: manual, Server
    • Labels:
      None

      Description

      Description

      Downstream Change Summary

      Should be added to https://docs.mongodb.com/manual/reference/parameters/

      Text from https://gperftools.github.io/gperftools/tcmalloc.html#runtime: "Rate at which tcmalloc releases unused memory to the system. Zero means it never release memory back to the system. Increase this flag to return memory faster; decrease it to return memory slower. Reasonable rates are in the range [0.0,10.0]. "

      (Default is 1)

      Description of Linked Ticket

      SERVER-16829 exposed tcmalloc_aggressive_decommit via the setParameter framework. This has turned out to be not very useful, as aggressive decommit comes with a huge performance penalty. (-75% in a small YCSB workload.)

      We recently found that tcmalloc_release_rate can be used to reduce memory overhead, with little or no performance overhead. We should add a setParameter knob to do this at runtime too.

      Relevant tcmalloc documentation

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Backlog - Core Eng Program Management Team Backlog - Core Eng Program Management Team
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 38 weeks, 1 day ago
                Date of 1st Reply: