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

Tracking issue: implicit and explicit snapshots #118

Open
11 tasks
vweevers opened this issue Sep 26, 2022 · 0 comments
Open
11 tasks

Tracking issue: implicit and explicit snapshots #118

vweevers opened this issue Sep 26, 2022 · 0 comments

Comments

@vweevers
Copy link
Member

vweevers commented Sep 26, 2022

Implicit snapshots

Main task here is to fix the issue described in Level/leveldown#796.

Explicit snapshots

This is a new feature. Prior discussions: #45, #47, Level/leveldown#486.

  • abstract-level (semver-minor): Define explicit snapshots abstract-level#42
  • level-supports (semver-minor): add explicitSnapshots property
  • abstract-level (semver-minor): implement explicit snapshots
  • memory-level (semver-minor): implement explicit snapshots (can just take a reference to the RB tree)
  • classic-level (semver-minor): implement explicit snapshots
  • browser-level (semver-patch): document that explicit snapshots are not available
  • level (semver-patch): document explicit snapshots
  • many-level (semver-minor): implement explicit snapshots
  • rave-level (semver-minor): implement explicit snapshots
vweevers added a commit to Level/abstract-level that referenced this issue Nov 10, 2022
vweevers added a commit to Level/abstract-level that referenced this issue Nov 10, 2022
vweevers added a commit to Level/classic-level that referenced this issue Nov 18, 2022
Has a tiny performance cost, which I negated by optimizing the
passing of options from JS to C++. The end result is faster than
before. However, I didn't check if it blocks the event loop for
a significant amount of time. Benchmarking concurrent gets might
answer that, later.

Ref Level/community#118.
vweevers added a commit to Level/abstract-level that referenced this issue Jan 27, 2024
vweevers added a commit to Level/classic-level that referenced this issue Feb 3, 2024
Has a tiny performance cost, which I negated by optimizing the
passing of options from JS to C++. The end result is faster than
before. However, I didn't check if it blocks the event loop for
a significant amount of time. Benchmarking concurrent gets might
answer that, later.

Ref Level/community#118.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant