-
Notifications
You must be signed in to change notification settings - Fork 40
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
Skaled slow processing transctions during catchup #1640
Comments
be investigate during 2.2 release |
3.17.0-beta.8
3.16.1
|
skaled: 3.17.0-beta.11 |
Relevant for 3.17.0-beta.11 3.16.1 - 0.5 seconds per block
|
@oleksandrSydorenkoJ could you please add skaled logs regarding the |
|
The fix is ready but not merged yet @olehnikolaiev please link the corresponding PR once you merged it, it can't be properly tested on DevNet due to low disk storage, waiting for QA testing |
skaled: 3.18.0-beta.0 |
Verified Skaled: 3.18.0 Each block contains from 50 to 1000 txs from 1000 users, tested via load tests in qa-test-automation. Short logs for comparison: |
Actual for skaled:3.20.0 with connected 3 indexer nodes Each of these nodes increased the number of catchuped blocks over some time: 17_node_slow_catchup.txt |
Related to #1560
Actual for Core, archive and sync nodes
Preconditions
Active chain with MTM
Versions
3.17.0-beta.8
3.17.0-develop.49
Steps to reproduce
Expected state:
Blocks should be catching up faster than new block are mined
Actual state
Skaled processed transactions in catchup block the same time as skaled mined new (or slower)
catchup_3_17_0_develop_49.txt
catchup_3_17_0_beta-8.txt
The text was updated successfully, but these errors were encountered: