We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
tidb/store/copr/key_ranges.go
Lines 137 to 144 in 21847fe
Since kv.KeyRange and coprocessor.KeyRange definition are different, we need to make object allocation to send coprocessor.Request...
We can avoid object allocation if kv.KeyRange and coprocessor.KeyRange are the same. Actually, they are both
kv.KeyRange
coprocessor.KeyRange
type KeyRange struct { StartKey []byte EndKey []byte }
The text was updated successfully, but these errors were encountered:
kv,store/copr: make kv.KeyRange the same with coprocessor.KeyRange, s…
fe4e6ba
…o we can use unsafe optimization (#37288) close #37286
Successfully merging a pull request may close this issue.
Enhancement
tidb/store/copr/key_ranges.go
Lines 137 to 144 in 21847fe
Since kv.KeyRange and coprocessor.KeyRange definition are different, we need to make object allocation to send coprocessor.Request...
We can avoid object allocation if
kv.KeyRange
andcoprocessor.KeyRange
are the same.Actually, they are both
The text was updated successfully, but these errors were encountered: