-
Notifications
You must be signed in to change notification settings - Fork 410
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
Extremely slow indexing on good hardware #536
Comments
Initial sync is a time consuming and heavy operation, but I'd expect the CPU usage to be higher. It may take several days. How are you invoking the esplora? are you running it in a single docker container as in the README? |
@philippem I was running it directly from bash:
rustc 1.82.0 (f6e511eec 2024-10-15) |
It will take several days for initial indexing and database compaction. Memory usage may go up to 15-20 GB then drop. WIth the Electrs can be stopped and restarted and it will resume where it left off. Once the initial sync is complete, subsequent starts will be much faster (only newer blocks be indexed). |
How long is it even supposed to take to do the
lightmode
index? I'm running a server with 2.5TB datacenter-grade SSD RAID, 64GB RAM, Intel Core i7-8700. Had Bitcoind already synced. It took probably 12hrs to index and compacttxstore
DB, and now it's 5th hour ofhistory
indexing and it seems to go waaay slower (currently on 300 of 4.8k .blk files) Not sure I understand what's the bottleneck here and the timeframe for the sync? CPU usage is <15%, mem 10%. Please advise!The text was updated successfully, but these errors were encountered: