feat: introduce on-disk cache persistance for major nym-api caches #6302
+437
−152
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
This includes: - mixnet contract cache - described nodes cache - nodes annotations cache (performance) those changes include taking some code developed for the purposes of #6277
jstuczyn
force-pushed
the
feature/persistent-nym-api-cache
branch
from
8d21ac5 to
d9b0bbf
Compare
benedettadavico
modified the milestones:
Oscypek (est. mainnet 27.01.2026),
Parmigiano - Mainnet release 10th Feb
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.
This includes:
those changes include taking some code developed for the purposes of #6277
Essentially whenever the aforementioned caches are refreshed, their contents are also written to disk so when the API restarts, it could load them (assuming the data is not older than the corresponding refreshing interval) instead of starting with no data
This change is