Reduce data refresh frequency and clean up code formatting#226
Merged
Conversation
- Change homepage polling intervals from 20s to 5min for both active users and global stats - Increase active-users API server-side cache from 1min to 5min - Remove getServerSideProps from turing page to eliminate SSR https://claude.ai/code/session_01UGfnsFfXcafbYbt2TuFUVq
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Summary
This PR reduces the polling frequency for real-time data updates and performs minor code cleanup to improve performance and maintainability.
Key Changes
getServerSidePropsexport from the Turing pageuseAnalysisControllerhook for consistencyImplementation Details
The polling interval changes reduce the frequency of API requests while maintaining reasonable data freshness. The 5-minute interval is more appropriate for metrics like global stats and active user counts that don't require real-time updates. The cache duration adjustment ensures the API endpoint respects the same refresh cadence.
https://claude.ai/code/session_01UGfnsFfXcafbYbt2TuFUVq