Optimize account_asset Index for improved performance #851
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In version 3.8.4, we re-evaluated the node's behavior on the testnet with PostgreSQL, SQLite, and MariaDB, focusing specifically on block 379106. This block featured 101 transactions utilizing DistributionToHolder, involving 10,327 accounts. These transactions resulted in:
Our analysis revealed that the account_asset table was not optimized for this volume of updates with the current indices.
To address this, we adjusted an index to include the fields account_id, asset_id, and latest. This optimization significantly improves the performance of updates and queries on this table, especially in high-throughput scenarios.
We also re-orgnaized a bit the config file for a better view on the database settings.