Tracking issue: implicit and explicit snapshots #118
Comments
This was referenced Sep 26, 2022
Closed
Closed
15 tasks
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.
12 tasks
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.
vweevers
added a commit
to Level/classic-level
that referenced
this issue
Oct 20, 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 Category: fix
vweevers
added a commit
to Level/classic-level
that referenced
this issue
Oct 20, 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 Category: fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implicit snapshots
Main task here is to fix the issue described in Level/leveldown#796.
abstract-level(v2): Breaking: require snapshots to be created synchronously abstract-level#54classic-level(v2): create snapshot synchronously (Breaking: bumpabstract-levelto 2.0.0 classic-level#52)Explicit snapshots
This is a new feature. Prior discussions: #45, #47, Level/leveldown#486.
abstract-level(semver-minor): Define explicit snapshots abstract-level#42level-supports(semver-minor): addexplicitSnapshotspropertyabstract-level(semver-minor): implement explicit snapshotsmemory-level(semver-minor): implement explicit snapshots (can just take a reference to the RB tree)classic-level(semver-minor): implement explicit snapshotsbrowser-level(semver-patch): document that explicit snapshots are not availablelevel(semver-patch): document explicit snapshotsmany-level(semver-minor): implement explicit snapshotsrave-level(semver-minor): implement explicit snapshotsThe text was updated successfully, but these errors were encountered: