You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all leaderboard data is sent to the frontend at once and paginated on the client side. This approach leads to heavy backend hits and can cause performance issues, especially as the amount of data grows.
Proposed Solution:
Implement backend-based pagination for the leaderboard data. This will allow the frontend to request only the necessary data for the current page, reducing the load on the server and improving performance.
Acceptance Criteria:
Implement API endpoint for paginated leaderboard data.
Modify the existing leaderboard component to fetch data from the new endpoint based on the current page.
Ensure that the pagination controls work seamlessly with the backend data.
Document the new API endpoint in the project's API documentation.
Benefits:
Reduced load on the server
Improved performance and faster load times for the leaderboard
Scalability for larger data
The text was updated successfully, but these errors were encountered:
Description:
Currently, all leaderboard data is sent to the frontend at once and paginated on the client side. This approach leads to heavy backend hits and can cause performance issues, especially as the amount of data grows.
Proposed Solution:
Implement backend-based pagination for the leaderboard data. This will allow the frontend to request only the necessary data for the current page, reducing the load on the server and improving performance.
Acceptance Criteria:
Benefits:
The text was updated successfully, but these errors were encountered: