-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
solana-ledger-tool verify command is too slow #3155
Comments
#3192 switches @sambley - how hard is it to create those profiling flame graphs? Any docs on how? I think the next step here is to grab a profile of |
This link has the required information to generate the profiling information |
@mvines, let me know if you want to take a look at it |
Looks like significant amount of time is spent in iterating over StatusCache::has_signature(). In this run it was taking around 55 secs to complete the verify. |
This change has an update to increase NUM_TICKS_PER_SECOND to 100 from 10 which seems to improve the peformance a bit |
Looks like the bottleneck is inside accounts squash, looking into it |
* build(deps): bump bytemuck from 1.18.0 to 1.19.0 Bumps [bytemuck](https://github.com/Lokathor/bytemuck) from 1.18.0 to 1.19.0. - [Changelog](https://github.com/Lokathor/bytemuck/blob/main/changelog.md) - [Commits](Lokathor/bytemuck@v1.18.0...v1.19.0) --- updated-dependencies: - dependency-name: bytemuck dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Update all Cargo files --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
solana-ledger-tool verify
takes ~5minutes to run during a testnet sanity check (cc: #2314). Culprit is very likelyprocess_blocktree()
.Decide if we should just disable ledger verification as a part of
./net.sh sanity
or try to optimize.Example: https://buildkite.com/solana-labs/testnet-management/builds/23148#4b97278e-1ad9-4eeb-9028-5a0467d81f85/228
The text was updated successfully, but these errors were encountered: