-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
vendor: bump Pebble to bb2c1501ac23 #81778
vendor: bump Pebble to bb2c1501ac23 #81778
Conversation
b5516a0
to
6d6dfb4
Compare
6d6dfb4
to
ebe0bf2
Compare
bb2c1501 tool/logs: print total flush / ingestion counts and durations d1cf3412 tool/logs: sort output by (start, node, store) 0a77780a tool/logs: fix total time calculation 0011c057 db: fix data race in SeekPrefixGE 99f35c80 internal/keyspan: gate invariant checks behind build tag 00302bfc internal/keyspan: use pointer receiver for most Span methods 3355a02e internal/rangekey: reduce range-key iteration allocations 4e33626f db: fix bug in interaction between Clone and indexed batches b14ad704 metamorphic: enable writer parallelism for randomzied metamorphic runs 9bd43143 db: reduce allocations in range key iteration e32e94d8 db: standardize behavior of indexed batch mutations during iteration a07efd96 internal/keyspan: lift visibility filtering out of Seek{GE,LE} Release note: none
ebe0bf2
to
41c642a
Compare
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.
Reviewed 5 of 5 files at r1, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @jbowens)
TFTR! bors r=nicktrav |
Build succeeded: |
I tracked down one of the microbenchmark regressions to this commit:
Is this concerning? |
@yuzefovich Is the regression still present on the current release-22.2 HEAD or master HEAD? There was a regression introduced in this pull request that was very recently fixed. |
The regression is still seen against both HEADs. However, there are other causes for the regression, so I think the next |
Release note: none