Status of speed regressions...

[Greg Ward]

On Fri, Nov 19, 2010 at 12:40 PM, Jason Harris <jason at jasonfharris.com> wrote:
> I was just wondering what the status of fixing the speed regressions is? Are there patches I can apply?
>
> As many of you will know the proscribed way for clients like, MacHg, Murky, SourceTree, etc is to work through the normal command interface, ie not link directly to the internals of Mercurial. As such if there is a 20% or more slow down in Mercurial, our tools become 20% slower (or more). Often due to refreshing and other issues these clients issue many mercurial commands a second. At least MacHg sometimes does in order to be in sync with changes, queries, etc.

The fix for this is simple and obvious: write an extension that
exposes a "Mercurial shell", where you can just run "status" or
"update" or "log" without the overhead of a new Python process.  Then
have MacHg or MercurialEclipse control this process through a pipe or
a socket.

In fact, ISTR that someone even posted the code here a few months ago.
 It was tiny: like 20 lines or something.  If you can package that
extension with your GUI, you're done.

Greg