Open drphrozen opened 5 months ago
Thanks @drphrozen for raising this, we have just released v0.4.3 where we restructured the user_sessions_this_run
model a bit in case it helps the query optimizer. If this doesn't help it's best to raise a support ticket if you can as it needs further investigation perhaps related to your warehouse setup.
I deployed 0.4.3 yesterday and it completed this morning.. Issue remains, i'll reach out to support and reference this issue,
Thanks. For comparison, it would be great to know which version of the web package you used, was it v1.0.1?
It's version 1.0.0
Describe the bug
In our dbt run of unified
snowplow_unified_users_sessions_this_run
takes 29742s out of 31658s (~94%).Steps to reproduce
In our case, add a lot of users and run unified model.
Expected results
That the peformance matched web dbt :)
Actual results
Its not
Screenshots and log output
dbt-output.txt
System information
The contents of your
packages.yml
file:Which database are you using dbt with?
The output of
dbt --version
:The operating system you're using: N/A
The output of
python --version
: N/AAdditional context
Compared to dbt web it looks like the calculation of start/end time was done incrementally, but is now calculated directly when needed.
Are you interested in contributing towards the fix?
Yes, if feedback is needed