Skip to content

Pts roachtest 3 #149340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 7 commits into from
Closed

Pts roachtest 3 #149340

wants to merge 7 commits into from

Conversation

aerfrei
Copy link
Contributor

@aerfrei aerfrei commented Jul 1, 2025

No description provided.

aerfrei added 6 commits June 27, 2025 14:04
Before this commit, we did not measure the performance
of protected timestamp creation or management. Since
DB-level changefeeds will potentially create many more
PTS records per job (one per watched table), we will
use these metrics to establish a baseline of how long
these operations take and to alert us to issues if
the new DB-level feeds overwhelm the PTS record table.

We will measure the speed of both creating the initial
PTS records in changefeed.stage.pts.create.latency and the
speed of advancing the PTS records when the frontier
progresses in changefeed.stage.pts.manage.latency.

We also include changefeed.stage.pts.manage_error.latency
for cases where the pts management errors.

Epic: none
Fixes: cockroachdb#147779
Informs: cockroachdb#147780

Release note (general): This change adds new metrics:
changefeed.stage.pts.create.latency,
changefeed.stage.pts.manage.latency,
changefeed.stage.pts.manage_error.latency,
to measure the performance of managing protected ts records.

<pkg>: <short description - lowercase, no final period>

<what was there before: Previously, ...>
<why it needed to change: This was inadequate because ...>
<what you did about it: To address this, this patch ...>
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@aerfrei aerfrei force-pushed the pts_roachtest_3 branch from 96ae946 to cebe650 Compare July 1, 2025 20:46
@aerfrei aerfrei closed this Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants