-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bqetl stage deploy
uses ever-increasing memory
#4340
Comments
In PR #4223 I tried not sharing one BigQuery client across all schema deployment threads, and closing BigQuery clients when the |
I've been doing some memory profiling on a smaller stage deploy with
I'll see if we can just pull in the schemas once and then keep reusing them across the queries that need to be deployed. |
Just to dump this here:
It looks like building the dependency graph, which happens on every |
Thanks for investigating! I was thinking it might help to have the |
bqetl stage deploy
seems to use ever-increasing amounts of memory as it runs, which can become an issue when deploying lots of artifacts to staging.For example, PR #4223's
deploy-changes-to-stage
CI job is attempting to deploy 401 artifacts to staging but keeps getting killed, apparently due to running out of memory.Even increasing the memory resources from 4 GB to 16 GB wasn't enough.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: