为什么Mercurial的汞修复这么慢? [英] Why is mercurial's hg rebase so slow?

查看:92
本文介绍了为什么Mercurial的汞修复这么慢?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Mercurial的rebase扩展提供了与git的rebase类似的功能.

The rebase extension to mercurial provides functionality similar to git's rebase.

让rebase执行需要100分钟的提交,大约需要4分钟(〜240 s).

Letting the rebase execute takes something like 4 minutes (~240 s) for 100 commits.

在我的想象中,这应该是非常快的,最多只有几秒钟,但是显然我错过了一些东西.

In my imagination this should be extremely fast, a few seconds at most, but clearly I'm missing something.

是什么导致了这么长时间?提交本身是否非常昂贵?

What makes it take so long? Are the commits themselves just extremely expensive?

推荐答案

默认情况下,将基准写入工作副本,但是您可以将其配置为在内存中运行以获得更好的性能,并允许它在工作时运行副本脏了. 只需在.hgrc文件中添加以下行:

By default, rebase writes to the working copy, but you can configure it to run in-memory for better performance, and to allow it to run if the working copy is dirty. Just add following lines in your .hgrc file:

[rebase]

experimental.inmemory = True

(要获得更多配置以进行变基,请尝试运行hg help rebase)

(To get more configuration for rebase try to run hg help rebase)

这篇关于为什么Mercurial的汞修复这么慢?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆