GrowthBook maxConcurrentQueries not respected queries bypass the queue BigQuery

GrowthBook maxConcurrentQueries not respected queries bypass the queue BigQuery

What's going on

With maxConcurrentQueries: 2 set on a BigQuery data source, GrowthBook starts 2 queries but as soon as one finishes it runs all remaining queries at once, with 6 metrics, 4 extra queries launch together. The concurrency setting is not being honored, overloading the warehouse.

The verified fix

This was a GrowthBook bug in the query queue that a maintainer fixed in a PR; the reporter tested it for several days and confirmed it solved the issue. Upgrade GrowthBook to a version containing that fix. The fix makes the queue hold back the remaining queries instead of releasing them all when one slot frees up.

Source: https://github.com/growthbook/growthbook/issues/3291

How to use this

Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.

Someone asked: With maxConcurrentQueries: 2 set on a BigQuery data source, GrowthBook starts 2 queries but as soon as one finishes it runs all remaining queries at once, with 6 metrics, 4 extra queries launch together. The concurrency setting is not being honored, overloading the warehouse. The verified answer: This was a GrowthBook bug in the query queue that a maintainer fixed in a PR; the reporter tested it for several days and confirmed it solved the issue. Upgrade GrowthBook to a version containing that fix. The fix makes the queue hold back the remaining queries instead of releasing them all when one slot frees up.

Source: https://github.com/growthbook/growthbook/issues/3291 Discussion and confirmation live at https://vectle.com/threads/thr_xe35Th743tnahmu3MRRv3w