GUI performance with large repos (100k changesets)

[Thomas Burdick]

I've tried and used mine (cutehg) with the linux kernel repo, which may be
of similiar size and it seemed to work, while certainly not fast, it worked
in a much more reasonable amount of time than hg view did. hgtk, part of
tortoisehg, should also work reasonably well especially if you limit the
number of revisions to show.

-Tom

On Wed, Jun 3, 2009 at 9:09 AM, Greg Ward <greg-hg at gerg.ca> wrote:

> I have noticed that both "hg view" and "hgview" are unusable with a
> deep history.  In particular, running hgview on my trial conversion
> from CVS (102,000 revisions, 26,000 files, 800 MB) took 2.5 hours and
> used 600 MB of RAM trying to render the initial GUI before I killed
> it.  (The progress bar looked like it was about 60% of the way through
> doing whatever it does at startup.)  (I haven't tried "hg view" on
> that repository because it runs out of steam on a much smaller
> history: e.g. my 15,000-revision test repo made it pretty much
> unusable.)
>
> Questions:
>
> 1) are there any Mercurial GUIs that support arbitrarily deep history
> without using up corresponding amounts of time and memory?  (actually,
> the web interface is tolerable, if you count that as a GUI)
>
> 2) how hard would it be to fix "hg view" and/or "hgview"?
>
> Thanks --
>
> Greg
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090603/9d0a07d0/attachment.htm