Skip to content

kv: investigate kv95 performance after Feb 18 #62359

@erikgrinaker

Description

@erikgrinaker

kv95 performance dropped significantly on Feb 18, as seen here: https://roachperf.crdb.dev/?filter=&view=kv95%2Fenc%3Dfalse%2Fnodes%3D1%2Fcpu%3D32&tab=gce

The initial drop was investigated in #62148, and was due to tracing. This was solved by #61777 (verified by cherry-picking onto the culprit PR #59992), but performance did not fully recover, so there were other performance regressions in the period following Feb 18. We need to figure out what these are and get back to the pre-Feb 18 baseline.

Metadata

Metadata

Assignees

Labels

C-investigationFurther steps needed to qualify. C-label will change.C-performancePerf of queries or internals. Solution not expected to change functional behavior.GA-blocker

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions