Release v0.20.0-f4

🚀 What's New & Improved

1. Database Upgrade: From redb to rocksdb

The core database for our indexing program has been fundamentally updated, migrating from redb to the more performant and robust rocksdb. This change is designed to resolve previous performance bottlenecks and significantly improve the efficiency of data handling during intensive indexing operations, leading to a faster and more reliable experience.

⚠️ Important Upgrade Instructions (Breaking Change)

This release introduces a BREAKING CHANGE due to the underlying database migration.

• Data Rebuild Required: Users currently running the indexing program MUST re-run the program to rebuild all data from scratch. Data generated with previous versions using redb is incompatible with this new rocksdb-based version. Attempting to use old data will result in errors and unexpected behavior. We recommend starting with a clean data directory after upgrading.

⚙️ Deployment Recommendations (Minimum Requirements)

• Memory (RAM): 32GB or more.
• Disk Space: 2TB or more.

🔧 Configuration Advice for Optimal Performance

To further enhance your indexing setup and avoid common performance issues, please consider the following parameter adjustments:

• --commit-interval: We strongly advise setting the --commit-interval parameter to a value of 100 or less. While larger values can lead to excessively long data write durations, severely impacting overall indexing speed and efficiency, a value of 100 or less ensures more frequent, smaller writes, which are generally more performant.
  • Example: --commit-interval 100
• --index-sats: To maintain peak indexing efficiency, it is NOT recommended to enable the --index-sats flag. Our analysis indicates that enabling this feature significantly impacts the overall performance and efficiency of the indexing process, leading to slower operation and increased resource consumption.

Full Changelog: v0.20.0-f3...v0.20.0-f4