feat: add 5s cache for sync status verification#761
Open
Sotatek-HenryDo wants to merge 1 commit into
Open
Conversation
Contributor
✅ Preprod Tests: PASSEDTests run against preprod network with live blockchain data |
Contributor
✅ Preprod Tests: PASSEDTests run against preprod network with live blockchain data |
17988d4 to
aea4cbf
Compare
aea4cbf to
81108ef
Compare
Contributor
💥 Preprod Tests: DEPLOYMENT FAILEDTests run against preprod network with live blockchain data |
Contributor
✅ Preprod Tests: PASSEDTests run against preprod network with live blockchain data |
Contributor
❌ Preprod Tests: FAILEDTests run against preprod network with live blockchain data |
Contributor
❌ Preprod Tests: FAILEDTests run against preprod network with live blockchain data |
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.
Ref: #759
Introduced a short-lived (5-second by default, configurable) cache for the indexer sync status verification.
Once the indexer transitions to the "LIVE" stage, subsequent status verifications (
verifySyncStatus()) utilize the cached status instead of querying the database. This significantly reduces database load and prevents repetitive checks on high-frequency endpoints (such as/blockand/account/balance) under heavy load.