GUI performance with large repos (100k changesets)

[Greg Ward]

[me, on 3 June]
> 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

On Fri, Jun 5, 2009 at 6:50 AM, Aurélien
Campéas<aurelien.campeas at logilab.fr> wrote:
> How long does it take to execute :

Sorry for the delay.  I didn't have a copy of the converted repository
around anymore and had to re-run the conversion.  Also, I have not yet
tried out the new hgview 1.0.0.  That said, here are some numbers:

  hg log           takes 65 sec (97% cpu)
  hg glog         takes 256 sec (99% cpu)

I'm using rev bb74be3abf60 of hgview (from 20 Mar 2009), so this might
all be irrelevant.  Anyways:

  * ~35 sec to render any GUI (including starting to show progress on
the progress bar)
  * quickly expands to use ~500 MB of memory and steadily growing (up
to 600 MB while writing this sentence)
  * takes the GUI ~60 sec to redraw after hiding/exposing
  * I killed it after letting it run for ~11 min: it was using 1283 MB
of virtual memory and the progress bar was about 10% done (from
counting pixels)

Guess I should try the latest hgview.

Greg