Closed Bug 1589994 Opened 5 years ago Closed 5 years ago

Use in-memory rebasing in Mercurial

Categories

(Conduit :: moz-phab, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: glob, Assigned: glob)

Details

(Keywords: conduit-triaged)

Attachments

(1 file)

moz-phab should use in-memory rebasing for its rebasing work when Mercurial 4.5 or higher is used.

A new experimental config option (rebase.experimental.inmemory=true)
enables rebases to be performed in-memory. Historically, Mercurial (and
Git) touch the working directory when doing history rewriting. On large
repositories or for rebases when the working directory and changesets in
the rebase have many changes, this can make rebase very slow. In-memory
rebasing removes a lot of that overhead.

I did some quick testing with mozilla-central and saw the time for some operations consistently drop from ~250 seconds down to ~30 seconds.

Assignee: nobody → glob
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: