On Tue, Feb 17, 2009 at 2:19 PM, Marko Käning <mk...@mch.osram.de> wrote: >> As I recall it, the performance penalty is payed by parsing the manifest >> file, not by searching directories. Thus clever selection of directories >> would not improve performance for visible overlays, but it would allow finer >> granularity over when to show overlays. > > I see. Good to know. > > (So, the sometimes quite long delays I have on my rather old 700 MHz PIII > are actually due Python's execution of THG, followed by the manifest > scanning, instead of Window's explorer overlays.) > > But still I could imagine that there might be a little gain if Windows > would not have to identify possible Mercurial repositories in every folder > displayed in its views. But still, probably it doesn't make a big > difference since I have TortoiseCVS and TortoiseSVN installed as well...
Every Tortoise client slows down Explorer a little, even though TortoiseHg may be much so comparing to TortoiseCVS and TortoiseSVN. Unfortunately at this point of time we are largely dependent on Mercurial's core performance, so I don't see too many options in speeding up the overlay icons display for TortoiseHg. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
