JMH and missing results: treat them as zeroes, instead of blankly skipping over them

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Unresolved
    • Priority: P4
    • None
    • Affects Version/s: None
    • Component/s: tools
    • None
    • jmh

      The result aggregation troubles highlighted by CODETOOLS-7901374 prompts to reconsider how we treat missing results.
      The fix for CODETOOLS-7901374 "just" ignores the absent values. It should instead treat them as "zero" results, because
      it affects "average" calculations. This is low priority, since most our profilers are reporting the stable set of results, at least
      during the measurement phase.

        1.
        		 Unbias secondary results in IterationResult Sub-task New Unassigned  
        2.
        		 Unbias benchmark results in RunResult Sub-task New Unassigned  

            Assignee:
            Aleksey Shipilev
            Reporter:
            Aleksey Shipilev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: