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

RocksDB huge memory usage #721

Closed
bidoudan opened this issue Dec 31, 2021 · 3 comments
Closed

RocksDB huge memory usage #721

bidoudan opened this issue Dec 31, 2021 · 3 comments

Comments

@bidoudan
Copy link

bidoudan commented Dec 31, 2021

Hello there,
Requesting /api/v2/address/<address>?details=txs for several times, RocksDB uses a lot of memory,
We've tried to run blockbook with -dbcache=0 -workers=1 -notxcache but nothing changed
Is there any solution for this issue.
Thanks in advance.

@martinboehm
Copy link
Contributor

Hi, you are not very specific neither by what is "huge" memory usage nor what coin you are using. However, RocksDB is memory hungry and you should use server that is reasonably dimensioned. From the settings you mentioned, only -dbcache=0 has effect on memory consumption of synchronized Blockbook (-workers=1 has effect only during initial synchronization).

@bidoudan
Copy link
Author

bidoudan commented Jan 9, 2022

Thanks for your response, we are using ravencoin, when we send request that I mentioned before for several times in some addresses used in great number of transactions, RocksDB takes more than usual to respond and it uses a lot of memory we are wondering if it was an indexing problem, because -dbcache doesn't have any effect in our case ?
(why RocksDB doesn't liberate allocated memory?)
Is it normal for such kind of addresses or we should change something.
Thanks

@prusnak
Copy link
Member

prusnak commented Feb 23, 2022

Essentially a duplicate of #43

Yes, Blockbook needs 32 GB of RAM for Bitcoin.

@prusnak prusnak closed this as completed Feb 23, 2022
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