hg outgoing performance: bug or design limitation?

[Benoit Boissinot]

On Tue, Dec 15, 2009 at 8:26 AM, Andrei Loskutov <loskutov at gmx.de> wrote:
> On Mon, 14 Dec 2009 23:55:43 +0100, Matt Mackall <mpm at selenic.com> wrote:
>
>>> Ok, I've played with incoming now. Here we have another, even bigger
>>> performance issue: in order to provide meaningful diffs for the incoming
>>> changesets, we call hg with this arguments:
>>>
>>> D:\django1\hg -y incoming --debug --style style_file --bundle
>>> D:\bundleFile.tmp D:\django2
>>>
>>
>> Again, you're getting slowed down by --debug and --style (somewhat
>> less). If you're using --debug, you can definitely expect to lose on
>> performance.
>
> Ok, I've removed --debug, but it doesn't really change anything. It is the
> --bundle argument which takes hg performance down.
> How can we avoid using it? Is there any better way to compute the diffs for
> *incoming* changesets "on the fly", just by using the file path and the
> changeset info?

Why do you need --bundle if both repos are local ?

regards,

Benoit