Skip to content
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

memdb: use ordered data structure #52

Closed
erikgrinaker opened this issue Mar 3, 2020 · 0 comments · Fixed by #53
Closed

memdb: use ordered data structure #52

erikgrinaker opened this issue Mar 3, 2020 · 0 comments · Fixed by #53
Assignees

Comments

@erikgrinaker
Copy link
Contributor

erikgrinaker commented Mar 3, 2020

MemDB currently uses a Go map for storage, which means all ordered operations (such as range scans) are extremely slow - see e.g. tendermint/tendermint#4520.

By using an ordered data structure instead, e.g. a B-tree, these operations would be significantly faster.

@erikgrinaker erikgrinaker self-assigned this Mar 4, 2020
faddat pushed a commit to faddat/tm-db that referenced this issue Feb 21, 2024
Bumps [actions/stale](https://github.com/actions/stale) from 7 to 8.
- [Release notes](https://github.com/actions/stale/releases)
- [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md)
- [Commits](actions/stale@v7...v8)

---
updated-dependencies:
- dependency-name: actions/stale
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant