-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[beta] backports #150214
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
base: beta
Are you sure you want to change the base?
[beta] backports #150214
Conversation
(cherry picked from commit 2a2da78)
(cherry picked from commit f33abb1)
…owedBuf` and `BorrowedCursor`) This caused several performance regressions because of existing code which uses `Read::read` and therefore requires full buffer initialization. This is particularly a problem when the same buffer is re-used for multiple read calls since this means it needs to be fully re-initialized each time. There is still some benefit to landing the API changes, but we will have to add private APIs so that the existing infrastructure can track and avoid redundant initialization. (cherry picked from commit 4b07875)
|
|
@Kivooeo, we (release team) do these backports mechanically based on the owning team's approvals, and that one doesn't have |
|
oh, it still wasn't been approved on a backport, yeah, i see it makes sense i just got concerned in a moment that less performant version will get into the beta and the one with better performance is not but now i feel like we still have a bunch of time, and it shouldnt be a problem, right? like, the second version will anyway gets in beta |
|
Yes, we're still quite early in the beta phase -- 1.93 release isn't until January 22. |
|
@bors r+ rollup=never p=1 |
BorrowedBufandBorrowedCursor#148937 -- Revert #148937 #150096r? cuviper