chore: Revert to only using 1 timezone support for template DAUs #7721
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Keeping the logic to support more in case we optimize later
coadler
approved these changes
May 30, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It took 58min on our dev server. Way longer than I anticipated. Local and tests are quick, so this was unexpected. I just removed the tz offsets from template DAUs for now. I think we should probably figure out a way to optimize this, as this doesn't make sense. Might just be a missing index on Postgres.
Until then, this keeps the DAU calculation correct and reverts the template DAUs to just 1 timezone offset. The deployment DAU takes 250ms to do all 24 timezones.