Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: use triesInMemory in downloader #56

Closed
wants to merge 5 commits into from

Conversation

welkin22
Copy link
Contributor

Description

Currently, our downloader has a hardcoded value of fsMinFullBlocks set to 64, which is half of 128. Since 128 represents TriesInMemory, which is now a configurable option in our geth version, the value of fsMinFullBlocks should change accordingly. For example, if we set TriesInMemory to 32, then the value of fsMinFullBlocks should be 16. We need to resolve this issue.

Rationale

We will store the values of the TriesInMemory configuration item and the fsMinFullBlocks field in the Downloader, and then replace all previous references to the hardcoded fsMinFullBlocks.

Example

none

Changes

Notable changes:

  • Added TriesInMemory and fsMinFullBlocks field to Downloader.
  • Replace all references to hard-coded fsMinFullBlocks

redhdx
redhdx previously approved these changes Jan 29, 2024
bendanzhentan
bendanzhentan previously approved these changes Jan 30, 2024
@welkin22 welkin22 dismissed stale reviews from redhdx and bendanzhentan via fa60b74 January 30, 2024 07:37
@welkin22 welkin22 marked this pull request as draft February 1, 2024 06:27
@welkin22
Copy link
Contributor Author

welkin22 commented Feb 1, 2024

Due to #58 modifying the relevant logic, this PR needs to wait for that PR to be merged before deciding whether to merge.

@welkin22
Copy link
Contributor Author

Close, as we no longer need the triesInMemory parameter.

@welkin22 welkin22 closed this Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants