-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Tweak dbt configuration parameters to reasonable values #9846
Conversation
…t docs/recommendatins)
/test connector=bases/base-normalization
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
atm we don't have benchmarks to verify the impacts of these changes, right
No, we don't now. It's fairly easy to create a new one by creating one mock source that 1) has the same catalog of the problematic real source, and 2) make it emit the same number of records that's giving snowflake normalization trouble. Feel free to do that in the [Benchmark] Destination Warehouse
workspace.
/test connector=bases/base-normalization
|
/publish connector=bases/base-normalization
|
What
Normalization parameters for multi-threading were set by default to 32
In the past (before implementing internal staging for snowflake, we've seen time-out errors from snowflake trying to shut us off from spamming their API (with insert writes).
So, following up on https://github.com/airbytehq/oncall/issues/120, I'm wondering if dbt is sometimes hitting some similar thresholds/limits randomly?
For instance, In the docs, I've seen recommendations or people mentioning using 5 to 10 threads:
From dbt docs:
From Snowflake docs:
How
This PR is tuning the parameters down to match recommendations or default values in dbt docs for some destinations.
It also tunes dbt to take advantage of some retries mechanisms with backoff timeouts.
Hopefully, these small changes would improve overall performances and stability
(atm we don't have benchmarks to verify the impacts of these changes, right @tuliren?)