Love GrowthBook, here with our first issue!
On a data-heavy experiment with two primary metrics and three guardrail metrics, we have two failing queries:
500: Code: 241. DB::Exception: Memory limit (total) exceeded: would use 7.46 GiB (attempt to allocate chunk of 0 bytes), maximum: 7.00 GiB: While executing AggregatingTransform. (MEMORY_LIMIT_EXCEEDED) (version 188.8.131.52.altinitystable (altinity build))
These failing queries run quickly in ClickHouse itself. The difference appears to be that GrowthBook runs the queries in parallel.
Solutions to our problem (beyond increasing RAM) are something like:
1. Not running GrowthBook queries in parallel
2. Allowing some way to manually update guardrail metrics (so we can run them one at a time ourselves)
Happy to provide more info if needed!
10/21/2022, 7:57 PM
Hey John. Are you self-hosting or using our Cloud?
10/21/2022, 7:58 PM
We're using the cloud.
10/21/2022, 8:02 PM
Ok, I think we'll need to add a setting to limit query concurrency. I'll make a GitHub issue for that
10/21/2022, 8:03 PM
That would be great! Thank you. Appreciate you + your team's hard work. 🙂