GUI performance with large repos (100k changesets)

[Steve Borho]

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)

The TortoiseHg log viewer deals very well with large repositories.
Much of the revision data is demand loaded, and it loads revisions in
batches.  There have been further performance improvements on the 0.8
development branch that make it acceptably fast with really large
changesets as well.

hg clone http://bitbucket.org/tortoisehg/crew  thg-devel
ln -s thg-devel/hgtk ~/bin
hgtk help

> 2) how hard would it be to fix "hg view" and/or "hgview"?

can't comment.