Optimize heartbeat duration calculations and indexes #916
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.
Fixes HACKATIME-19H. The issue was that: Complex window functions without optimal index support cause sequential scans and sorts, leading to slow queries.
heartbeatsfor(user_id, language, time)to optimize window functions partitioned by language.daily_durations_for_usersto improve index usage by simplifying the inner window function'sPARTITION BYtouser_idand moving day grouping to the outer aggregation.total_duration_for_scopeto dynamically includeuser_idin window functionPARTITION BYclauses whenuser_idis present in the query'sWHEREclause, leveraging composite indexes.This fix was generated by Seer in Sentry, triggered by mahadkalam1234@gmail.com. 👁️ Run ID: 9956850
Not quite right? Click here to continue debugging with Seer.