-
Notifications
You must be signed in to change notification settings - Fork 83
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
[indexer]: backend database alternative #2439
Labels
Milestone
Comments
popcnt1
added
optimize
feature
New feature
area::ideas
Application or Feature ideas
labels
Aug 15, 2024
For sqlite: p.s. in rebuild process, sqlite handles well enough(cost 18000s for 0.3B items import): Test Result(After rebuild):
disk iostat: util: 100% 6k-12k read/s, 300MB/s read
For indexer built from 10M utxo + 3M inscription(16000029 items,8.5G space):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background:
the mainnet data set is huge, in presnet, is about 0.3B items, and cost 180GB space for sqlite. Will sqlite works well with these size of data and continue supprts high qps?
The text was updated successfully, but these errors were encountered: