Evaluate options for improving performance with large time-series measurements

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution Team 2022-06-13, Execution Team 2022-06-27
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently if we have large measurements, we can end up keeping relatively few measurements per bucket. We may wish to increase the default value of the timeseriesBucketMaxSize parameter. Alternatively, we may wish to only consider closing the bucket due to size if we have a certain minimum number of measurements (e.g. 5) or if it would cause the bucket to violate the object size limit (16MiB).

            Assignee:
            Gregory Wlodarek
            Reporter:
            Dan Larkin-York
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: