Problem: Validator projection catching up speed is slow #593
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.
Solution: fixed #586
The main bottleneck is in handling
BlockCreated
event, we have some code that is updating all active validators' uptime. Previously, we are doing it in a loop manner, each validator will do one update SQL.In my improved version, there are mainly two changes:
Update multiple rows reference: https://stackoverflow.com/a/26715934
Benchmark
the improvement is at
BlockCreated-updateValidator
columnTable columns:
Before optimization:
After optimization:
Benchmark data files (local indexer running against Crypto.org mainnet):
before-optimize-validator.csv
after-optimize-validator.csv