Repository navigation
perf(issues): cache bounty list response with 30s revalidation window (#716) - #818
Open
PINYOPATTANAWASANPORN wants to merge 1 commit into
Open
PINYOPATTANAWASANPORN wants to merge 1 commit into
PINYOPATTANAWASANPORN wants to merge 1 commit into
Conversation
|
@PINYOPATTANAWASANPORN is attempting to deploy a commit to the chonilius' projects Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been deployed
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 of Changes
Sets route segment config export const revalidate = 30; on the /issues page (src/app/issues/page.tsx).
Root Cause & Technical Context
IssuesPage fetches the entire backend bounties table via fetchBounties. Because the backend endpoint is currently unpaginated, every page visit and pagination click transfers and parses the entire table on each request. As outlined in #716, until upstream pagination is completed in the backend, adding a 30-second revalidation cache bounds unnecessary round trips and prevents linear server cost growth while keeping bounty statuses and claim updates fresh.
Verification
Closes #716