-
Notifications
You must be signed in to change notification settings - Fork 7
Add prefixOffset option #97
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
Conversation
Odd, that test failure is unrelated to this change. |
Seems to be a problem in the test runner... |
Yeah, seems unrelated. But here's a proposed fix: - state = validate.appendNew(state, null, keys, msg1, Date.now() + 3000)
- state = validate.appendNew(state, null, keys, msg2, Date.now() + 2000)
- state = validate.appendNew(state, null, keys, msg3, Date.now() + 1000)
+ const now = Date.now()
+ state = validate.appendNew(state, null, keys, msg1, now + 3000)
+ state = validate.appendNew(state, null, keys, msg2, now + 2000)
+ state = validate.appendNew(state, null, keys, msg3, now + 1000) |
I think the problem is bigger than that. Working on a fix in a different branch |
Benchmark results
|
I'll do a PR against db2 when this is ready for key & others that might have use of this :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Benchmark results
|
Makes it possible specifiy where in the target the prefix buffer should be constructed from.
Some motivation here, it will make some certain prefix indexes much faster.