cockroachdb / cockroachdb/cockroach
perf: revisit the default compaction concurrency value
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
We ran into multiple incidents that hitting compaction concurrency limit. Here are a couple recent events:
1. https://github.com/cockroachlabs/support/issues/3264#issuecomment-2851964925
2. https://github.com/cockroachlabs/support/issues/3356
We should revisit the default value and determine if we should increase it.
Jira issue: CRDB-51973
Contributor guide
Research direction
Start by reviewing the two linked support incidents and the context in Jira issue CRDB-51973. Then locate the compaction concurrency default and examine how the limit relates to the reported incidents. Done means agreeing on an evidence-based default value and validating the change against relevant compaction behavior or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100