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
5 of 11 tasks
vweevers opened this issue Sep 26, 2022 · 0 comments
Open
5 of 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, explained by the first PR below. Prior discussions: #45, #47, Level/leveldown#486.

@vweevers vweevers added this to Level Sep 26, 2022
@vweevers vweevers moved this to Backlog in Level Sep 26, 2022
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.
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
vweevers added a commit to Level/supports that referenced this issue Dec 21, 2024
vweevers added a commit to Level/supports that referenced this issue Dec 21, 2024
vweevers added a commit to Level/abstract-level that referenced this issue Dec 22, 2024
vweevers added a commit to Level/memory-level that referenced this issue Dec 22, 2024
@vweevers vweevers moved this from Backlog to In Progress in Level Dec 22, 2024
vweevers added a commit to Level/supports that referenced this issue Dec 23, 2024
vweevers added a commit to Level/abstract-level that referenced this issue Dec 23, 2024
vweevers added a commit to Level/memory-level that referenced this issue Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant