Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

client/cli: default db-cache value unfit for archive node #10653

Closed
ggwpez opened this issue Jan 13, 2022 · 0 comments · Fixed by #10659
Closed

client/cli: default db-cache value unfit for archive node #10653

ggwpez opened this issue Jan 13, 2022 · 0 comments · Fixed by #10659
Labels
I4-annoyance The client behaves within expectations, however this “expected behaviour” itself is at issue. U3-nice_to_have Issue is worth doing eventually. Z1-easy Can be fixed primarily by duplicating and adapting code by an intermediate coder

Comments

@ggwpez
Copy link
Member

ggwpez commented Jan 13, 2022

Exporting blocks from an archive node with the default parameters is very slow.

./target/release/polkadot export-blocks --from 7000000 --to 8000000 --pruning archive --binary | pv > /dev/null

reports 50 KiB/s on average.

A tip from @arkpar revealed that --db-cache=4096 fixes it and increased performance up to 350 MiB/s on my hardware.
What do you think is a good default for archive? Just the 4096 or something else?

@ggwpez ggwpez added I4-annoyance The client behaves within expectations, however this “expected behaviour” itself is at issue. U3-nice_to_have Issue is worth doing eventually. Z1-easy Can be fixed primarily by duplicating and adapting code by an intermediate coder labels Jan 13, 2022
@ggwpez ggwpez changed the title Abysmal export-blocks speed for archive node client/cli: default db-cache value unfit for archive node Jan 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
I4-annoyance The client behaves within expectations, however this “expected behaviour” itself is at issue. U3-nice_to_have Issue is worth doing eventually. Z1-easy Can be fixed primarily by duplicating and adapting code by an intermediate coder
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant