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.

Sign up for GitHub

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

Jump to bottom

Delay piece cache sync to after node is synced #50

Closed
nazar-pc opened this issue Dec 18, 2023 · 1 comment
Closed

Delay piece cache sync to after node is synced #50

nazar-pc opened this issue Dec 18, 2023 · 1 comment
Labels
backend Backend logic enhancement New feature or request farmer Farmer functionality good first issue Good for newcomers ux UX-related

Comments

@nazar-pc
Copy link
Member

Right now piece cache sync will happen right after start, which is not 100% correct because node may not yet be aware of what the latest state of the archival history is.

Delaying it to after sync will both reduce node sync start delay and will avoid potentially replacing some of the pieces with others later on.
@nazar-pc nazar-pc added enhancement New feature or request good first issue Good for newcomers ux UX-related backend Backend logic farmer Farmer functionality labels Dec 18, 2023
@nazar-pc nazar-pc moved this to Todo in Space Acres Feb 15, 2024
@nazar-pc
Copy link
Member Author

nazar-pc commented Mar 3, 2024

Resolved fully in #136, now everything is happening concurrently and there is no strict dependency between components

@nazar-pc nazar-pc closed this as completed Mar 3, 2024
@github-project-automation github-project-automation bot moved this from Open Tasks to Complete in Space Acres Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend Backend logic enhancement New feature or request farmer Farmer functionality good first issue Good for newcomers ux UX-related
Projects
Space Acres
Status: Complete
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nazar-pc