[Merged by Bors] - increase cache size to 50 000 for next release #5079
Conversation
This file contains 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
dshulyak
requested review from
countvonzero,
fasmat and
poszu
as code owners
countvonzero
approved these changes
Sep 25, 2023
dshulyak
changed the title
|
bors merge |
bors bot
pushed a commit
that referenced
this pull request
Sep 25, 2023
there are many places that have to read atxs, if number of atxs in epoch larger then what we cache it causes cache threshing signficant and disk reads. for example in this epoch nodes in cloud peek every 5m with 140MB/s reads. i set it to 50 000 to account for possible growth in the next epoch.
Codecov Report
@@ Coverage Diff @@
## develop #5079 +/- ##
=========================================
- Coverage 77.1% 77.1% -0.1%
=========================================
Files 257 257
Lines 30277 30277
=========================================
- Hits 23349 23346 -3
- Misses 5402 5404 +2
- Partials 1526 1527 +1
|
|
Build failed (retrying...): |
bors bot
pushed a commit
that referenced
this pull request
Sep 25, 2023
there are many places that have to read atxs, if number of atxs in epoch larger then what we cache it causes cache threshing signficant and disk reads. for example in this epoch nodes in cloud peek every 5m with 140MB/s reads. i set it to 50 000 to account for possible growth in the next epoch.
|
Build failed: |
|
bors merge |
bors bot
pushed a commit
that referenced
this pull request
Sep 25, 2023
there are many places that have to read atxs, if number of atxs in epoch larger then what we cache it causes cache threshing signficant and disk reads. for example in this epoch nodes in cloud peek every 5m with 140MB/s reads. i set it to 50 000 to account for possible growth in the next epoch.
|
Pull request successfully merged into develop. Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
bors
bot
changed the title
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.
there are many places that have to read atxs, if number of atxs in epoch larger then what we cache it causes cache threshing
signficant and disk reads. for example in this epoch nodes in cloud peek every 5m with 140MB/s reads.
i set it to 50 000 to account for possible growth in the next epoch.