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

Change name or calculation of memory_used_to_memory_help_pct_at_peak to a value that's more identifiable

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Workload Scheduling

      as part of HELP-62699, we concluded that the value memory_used_to_memory_help_pct_at_peak in FTDC metrics can be quite confusing when viewing.

      We think this should be renamed to have more clarity.

      We get this value directly from TCMalloc, so we do not calculate it ourselves. Originally, it is calculated and labeled as generic.realized_fragmentation, and it is then relabeled here. As explained in the help ticket, this value can get upwards of several 100,000%+, even up to 1 million %.

      The way the value is calculated is the % of memory we allocated MORE than the actual usage. So if we allocate 50 MB, and only actually use 8KB, the realized_framgentation will be 600,00%+.

      Dimitry suggests maybe we recalculate so that its seen as the other way around, 8Kb is only 0.01% of 50Mb, so that people are seeing a value between 0 - 100.

      Wanted to open up a ticket for discussion about this a calculation change on top of renaming the metric.

        1. screenshot-1.png
          181 kB
          Dmitry Ryabtsev

            Assignee:
            Unassigned Unassigned
            Reporter:
            dominic.hernandez@mongodb.com Dominic Hernandez
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: