fix: use cached specialPosts promise in SSR to reduce CPU usage#3973
Merged
fix: use cached specialPosts promise in SSR to reduce CPU usage#3973
Conversation
…r request The specialPosts() function was being called directly on every SSR request in app_render.jsx, bypassing the cached promise (refreshed every 5 minutes) set up in server.js. Each call triggered 10+ sequential HTTP requests to the blockchain API, causing CPU saturation during traffic peaks.
kuny0707
approved these changes
Apr 3, 2026
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.
Summary
app_render.jsxwas callingspecialPosts()directly on every SSR request, bypassing the cached promise (app.specialPostsPromise) that refreshes every 5 minutes inserver.jsspecialPosts()call triggers 10+ sequential HTTP requests to the blockchain API (one per featured/promoted post + notices), causing CPU saturation during traffic peaks (2-3 hour daily spikes at 85%+ CPU)ctx.specialPostsPromise) and use it inapp_render.jsxinstead of callingspecialPosts()directlyChanges
src/server/server.js: Added middleware to passapp.specialPostsPromiseto request contextsrc/server/app_render.jsx: Replacedawait specialPosts(ctx.session.uid)withawait ctx.specialPostsPromise, removed unused importTest plan
Loading special postslog frequency — should appear every 5 minutes only (not per request)top/htopduring peak hours — should see significant reduction