Improve bulk load bucket size limit estimation

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • Storage Execution 2025-06-09, Storage Execution 2025-07-21, Storage Execution 2025-08-18
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Inserting a batch of measurements that compress well that should fit into one bucket may lead to creation of multiple buckets because the size estimation cannot make too many assumptions on compressibility of data. This is a problem during bulk load, and not during steady state since in steady state a partially full bucket is compressed, and adding one uncompressed measurement leads to less error in the size estimation.

      Consider a server parameter that allows the customer to influence the size estimation in relation to timeseriesBucketMaxSize.

              Assignee:
              Matt Kneiser
              Reporter:
              Matt Kneiser
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: