test: profile wallet sqlite database operations #3451
Merged
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.
Description
Profiled all wallet SQLite database read and write operations by virtue of easily identifiable log entries.
Motivation and Context
We currently have lots of database contention, resulting in poor system-level performance in many instances and also impacting the console wallet's TUI. Providing insightful logging was therefore necessary.
Part of this investigation focussed on poor metadata update performance. The log extracts below clearly shows that it is due to database contention and not database query performance:
How Has This Been Tested?
System-level tests