cockroachdb / cockroachdb/cockroach

Investigate / reduce overhead preventing higher CPU utilization

Open
#114,577 1 comment 0 reactions 0 assignees View on GitHub
C-enhancement O-23.2-scale-testing O-testcluster T-kv
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

Max CPU consumed by a cluster generally maxes out at ~75%, even with a plain KV workload that shouldn't hit I/O bottlenecks. This seems do be due to a bunch of overhead in our runtime stack. E.g. Refer to the screenshot below taken on a KV workload.

![image](https://github.com/cockroachdb/cockroach/assets/110843721/67eaaeae-37c8-4b8b-81b4-bf1d8a2df04d)

This is a concern to customers because we charge for 100% of the cluster, but from the customer's perspective, they can't use 100% of the cluster. Additionally, it puts us at a price/performance disadvantage vs competitors that exhibit less overhead. We should look at these sources of overhead and determine if it makes sense to / if there is opportunity to optimize anything.

More context is here: https://cockroachlabs.slack.com/archives/C04HQCNHGEP/p1699962493375829

Jira issue: CRDB-33572

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.