cockroachdb / cockroachdb/cockroach
server: smarter retention policy for cpu/mem profiles
Open
C-enhancement
O-support
P-3
T-db-server
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
We currently keep the last X heap profiles. Frequently the time period of interest is older than the oldest available profile.
Rather than keeping just the X newer profiles, we could (for example)
- keep X/2 newest profiles
- keep every other profile from the next X/2 profiles
- keep every 4th profile from the next X/2 profiles
- and so on
This applies to cpu profiles as well.
Jira issue: CRDB-51320
Contributor guide
Assessment
This issue has not been assessed yet.