Larger deployments have noticed that our migrations are a bit suboptimal, especially on clustered MySQL deployments. Both our larger deployments are also on 2.2 still.
This series speeds up migrations from ~7-8 mins to 1-1.5 mins for my 558 MB MariaDB test database. It also does the data migration in chunks which should make administrators' lives nicer. It currently breaks postgres/sqlite, but I'm hoping to get some feedback from larger deployments on whether I'm moving in the right direction here before I polish it up too much. Kind regards, Daniel Daniel Axtens (4): migrations: don't go to the db for 0041_python3 migration migrations: 0043_merge_patch_submission: do less work migrations: 0043: split the data migration into chunks RFC: migrations: 0043: Perform ALTER TABLE in one big batch patchwork/migrations/0041_python3.py | 632 +++++++++--------- .../migrations/0043_merge_patch_submission.py | 423 +++++++----- 2 files changed, 556 insertions(+), 499 deletions(-) -- 2.30.2 _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
