Skip to content
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

Increase checkpont details on tablespace #816

Open
diegosalvi opened this issue Nov 24, 2023 · 0 comments
Open

Increase checkpont details on tablespace #816

diegosalvi opened this issue Nov 24, 2023 · 0 comments

Comments

@diegosalvi
Copy link
Contributor

FEATURE REQUEST

Currently timings on checkpoints are someway misleading and missing.
This is a log extract:

23-11-24-12-11-16       galletto checkpoint start ts1 at (1528,27505)
23-11-24-12-11-19       checkpoint done for table ts1.x1 (pin: false)
23-11-24-12-11-22       checkpoint done for table ts1.x2 (pin: false)
23-11-24-12-11-22       checkpoint done for table ts1.x3 (pin: false)
23-11-24-12-11-27       checkpoint done for table ts1.x4 (pin: false)
23-11-24-12-11-27       checkpoint done for table ts1.x5 (pin: false)
23-11-24-12-11-57       galletto checkpoint finish ts1 started ad (1528,27505), finished at (1528,27505), total time 46351 ms

The whole tablespace checkpoint needed a whopping 46seconds but really 30 seconds were spent beetween last table checkpoint and the end of the tablespace checkpoint.
In such phase there are at least 2 jobs to be done:
dropOldLedgers (done under tablespace write lock)
PostCheckpointAction.runs (outside tablespace write lock)
Which operation required so much time? We really don't know.

We should expand checkpoints log on tablespace to better understand where time is spent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant