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

Use nextv() and decide on default hwm #1

Closed
vweevers opened this issue Jan 16, 2022 · 0 comments · Fixed by #2
Closed

Use nextv() and decide on default hwm #1

vweevers opened this issue Jan 16, 2022 · 0 comments · Fixed by #2

Comments

@vweevers
Copy link
Member

Follow-up for Level/abstract-level#12.

We can set the highWaterMark stream option to 1000 (like leveldown's caching), 16 (like streams) or something in between. We'll also need a separate option to control hwm measured in bytes.

@vweevers vweevers moved this from Backlog to Todo in Level Jan 16, 2022
@vweevers vweevers moved this from Todo to In Progress in Level Jan 29, 2022
vweevers added a commit that referenced this issue Jan 29, 2022
TODO: benchmarks, decide on default highWaterMark.

Ref Level/community#70
Ref #1
@vweevers vweevers moved this from In Progress to Review in Level Jan 30, 2022
vweevers added a commit that referenced this issue Jan 30, 2022
Repository owner moved this from Review to Done in Level Jan 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant