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

Modify forest and forest-cli to prefer compressed files #2873

Closed
2 tasks
Tracked by #2741
lemmih opened this issue May 15, 2023 · 3 comments · Fixed by #2893
Closed
2 tasks
Tracked by #2741

Modify forest and forest-cli to prefer compressed files #2873

lemmih opened this issue May 15, 2023 · 3 comments · Fixed by #2893
Assignees
Labels
Ready Issue is ready for work and anyone can freely assign it to themselves

Comments

@lemmih
Copy link
Contributor

lemmih commented May 15, 2023

Compressed snapshots are roughly half the size of uncompressed snapshots, and un-compressing them is fast. By default, we should prefer downloading/importing compressed snapshots.

  • Use https://snapshots.mainnet.filops.net/minimal/latest.zst by default when downloading from the official snapshot provider.
  • Use https://forest.chainsafe.io/mainnet/snapshot-latest.car.zst by default when downloading from our own servers.
@lemmih lemmih changed the title modify forest and forest-cli to prefer compressed files. Modify forest and forest-cli to prefer compressed files May 15, 2023
@lemmih lemmih added the Ready Issue is ready for work and anyone can freely assign it to themselves label May 15, 2023
@lemmih
Copy link
Contributor Author

lemmih commented May 16, 2023

It appears that filops no longer hosts uncompressed snapshots. We should update Forest to reflect this.

@aatifsyed
Copy link
Contributor

Does this require anything not already done in #2888 ?

@lemmih
Copy link
Contributor Author

lemmih commented May 16, 2023

Does this require anything not already done in #2888 ?

Let's move away from uncompressed snapshots entirely and remove the --compressed flag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ready Issue is ready for work and anyone can freely assign it to themselves
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

2 participants