Skip to content

Record transaction duration during migrations

What does this MR do and why?

Record transaction duration during migrations

  • Create a new file, during migrations, with the duration of each transaction

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

  1. Create a new migration
  2. Run rake gitlab:db:migration_testing:up
  3. Check tmp/migration-testing/ files

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to gitlab-org/database-team/gitlab-com-database-testing#33 (closed)

Edited by Diogo Frazão

Merge request reports