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

Investigate performance of new gperftools upstream MarkThreadTemporarilyIdle

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Performance
    • None
    • Fully Compatible
    • Platforms 11 (03/11/16)

      The upstream GPerftools master has merged a commit adding a new MarkThreadTemporarilyIdle function that may offer us improved performance over our current practice of calling MarkThreaIdle followed immediately by MarkThreadBusy.

      We should benchmark the following configurations and understand the effects:

      • Master, built against the system allocator
      • Master, built against the vendored tcmalloc, with the MarkThreadIdle/MarkThreadBusy subsystem disabled
      • Master, built against the vendored tcmalloc, using the current MarkThreadIdle/MarkThreadBusy subsystem.
      • Master, built against the gperftools master, with the MarkThreadIdle/MarkThreadBusy subsystem disabled
      • Master, built against the gperftools master, using the current MarkThreadIdle/MarkThreadBusy subsystem
      • Master, built against the gperftools master, using the new MarkThreadTemporarilyIdle API.

            Assignee:
            matt.cotter Matt Cotter
            Reporter:
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: