Consider options to invoke $queryStats less frequently in the fuzzer

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      DEVPROD-3327 changed the "internalQueryStatsRateLimit" parameter in the optimization fuzzer from -1 (unlimited) to 10 in order to reduce query stats store sampling, since the invocation of $queryStats (introduced in DEVPROD-2844) was causing timeouts by running after each query.

      There's no need to run $queryStats after each query since the query stats store will store tons of query shapes at a time. We could consider just running it once after runningĀ all generated queries, but that would risk losing coverage if we've evicted entries after reaching the query stats store memory limit. Instead, we could consider invoking $queryStats after every X queries. It might be worth roughly calculating how quickly the query stats store reaches capacity to estimate a reasonable value for X.

            Assignee:
            Erin Zhu
            Reporter:
            Will Buerger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: