Conversation
the previous code uses current_date but that's the date in UTC, thus it can differ from current_date in another timezone replacing CURRENT_DATE with DATE(now() at time zone TZ) would probably be the most direct fix but this fix will be faster once an index on first_seen is added using the DATE() function on a column won't gain this speedup
various fixes + improvements
* add index on last_seen / last_seen_distance * cache total aircraft/flights seen, refresh daily (total "aircraft" seen uniqueness was causing very slow queries as db grows. Also applied caching to total "flights" - even though less expensive as not unique) * stop interesting / routes / record holders from polling - not needed - data just fetched on tab load / refresh.
fix: api performance improvements
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.