ExportXMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      $dateTrunc can easily become a bottleneck for our synthetic queries and TPC-H queries. The current implementation is naive and calls into a separate library each invocation. This ticket is intended to be the umbrella ticket for several items:

      • Investigate reducing the overhead of calling into the library (e.g. is some state recreated each time?)
      • Investigate an optimized implementation when truncating by a fixed-size unit (e.g. minute, hour)
      • Investigate using the monotonic property of dateTrunc and caching the results of previous calls to avoid expensive trips into the library

            Assignee:
            Vedant Sharda
            Reporter:
            Ian Boros
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: