-
Notifications
You must be signed in to change notification settings - Fork 4.1k
storage: performance regression in EncodeMVCCKey and EncodeMVCCValue #88818
Copy link
Copy link
Closed
Copy link
Labels
A-storageRelating to our storage engine (Pebble) on-disk storage.Relating to our storage engine (Pebble) on-disk storage.C-performancePerf of queries or internals. Solution not expected to change functional behavior.Perf of queries or internals. Solution not expected to change functional behavior.GA-blockerT-storageStorage TeamStorage Teambranch-release-22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2
Metadata
Metadata
Assignees
Labels
A-storageRelating to our storage engine (Pebble) on-disk storage.Relating to our storage engine (Pebble) on-disk storage.C-performancePerf of queries or internals. Solution not expected to change functional behavior.Perf of queries or internals. Solution not expected to change functional behavior.GA-blockerT-storageStorage TeamStorage Teambranch-release-22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2
Type
Fields
Give feedbackNo fields configured for issues without a type.
Describe the problem
Currently, on the 22.2 release branch there is a sizable performance regression in
EncodeMVCCKey, relative to 22.1:The above was generated by comparing benchmark results between 22.1 (9eb4da2) to 22.2 (054f32b), via the following:
Jira issue: CRDB-19971
Epic CRDB-2624