Hello,
My company uses Mercurial heavily with a fairly large repository (hg
metadata is about 1.3 GB, a working copy contains ~57.000 files when clean,
and several hundred thousand files and be 20+ GB in size when dirty). We
also make fairly heavy use of the Mercurial largefiles extension.
When we run `hg status` on the command-line in a dirty repository, it takes
about 1.5 seconds (give or take a few hundred milliseconds depending on the
filesystem and other factors).
We have many Windows users who work more or less exclusively in TortoiseHG.
They complain that when they are using TortoiseHG, the UI is consistently
"freezing" for a couple of seconds as it updates the UI. We suspect this
is due to a large number of calls to `hg status`, each taking ~1.5 seconds.
Perhaps there has been an assumption that a call to `hg status` will be
fast (only a couple hundred milliseconds), so it is called frequently.
How could we work with you to diagnose and improve the situation?
Cheers,
Na'Tosha
--
*Na'Tosha Bard*
Software Developer | Unity Technologies - Copenhagen
*E-Mail:* [email protected]
*Skype:* natosha.bard
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
