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

horrible slow sync on pi3b+ and max memory ram usage #209

Open
phenomeus opened this issue Nov 29, 2019 · 6 comments
Open

horrible slow sync on pi3b+ and max memory ram usage #209

phenomeus opened this issue Nov 29, 2019 · 6 comments

Comments

@phenomeus
Copy link

phenomeus commented Nov 29, 2019

hi,

I'm suffering right now to get nbxplorer to sync up to the btc node (same pi) to start using btcpayserver. I know the hardware is very low but maybe there is a trick to speed up the sync. right now I'm restarting the nbxplorer.service every 10 minutes just to free up the ram and proceed with syncing because otherwise its hanging the whole pi because of 61,8% (htop shows 700mb+ ram usage out of 1024) and the 450+MB/2GB swap file is also getting filled

hope to get through soon with some ideas or just my workaround

@phenomeus phenomeus changed the title horrible slow sync on pi3b+ horrible slow sync on pi3b+ and max memory ram usage Nov 29, 2019
@pavlenex
Copy link

pavlenex commented Nov 29, 2019

This is already documented in official btcpay RPI3 docs, use fast sync.

cd /root/btcpayserver/btcpayserver-docker

./btcpay-down.sh
cd contrib
cd FastSync
./load-utxo-set.sh

@phenomeus
Copy link
Author

yeah I know but its not recommended. and I'm catching up: 601959 / 605903

so no other suggestions only fast sync right?

@pavlenex
Copy link

What do you mean it's not recommended? It's the only way to make it work on RPI3 afaik.

@phenomeus
Copy link
Author

I bought a pi 4 4GB yesterday, I will retry it with the beefier hardware, but thanks

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

No branches or pull requests

3 participants