15

It looks like having kbfiles causes quite a lot of status-related Mercurial commands be much slower. For example, "hg status". A lot of GUI clients use hg status a lot, which also makes those clients feel much more sluggish.

Our repositories are quite large (~11000 files, ~700 megabyte working copy + .hg folder, additionally ~1GB worth of kbfiles). On MacBookPro Core i7 2.66GHz, with SSD disk, on no-changes repository clone:

hg status: 0.3 seconds, with kilnbfiles disabled in .hgrc
hg status: 3.8 seconds, with kilnbfiles

So presence of kilnbfiles makes hg status 10 times slower!

Maybe there are some low hanging fruits in what kbfiles does in hg status/summary and other commands, that could be optimized away?

Fog Creek Case FC2033270

flag
3 
 I'd just like to vote for this being fixed. I noticed hg being much slower after a recent client tools install. I finally tracked it down to the kbfiles extension. – Craig Quillen Aug 3 at 14:33

2 Answers

4

Thanks for the report!

We've got a case filed for this issue and are looking into it now. At the moment, we think that the root cause is that .hgignore is not being honored when calling hg status if the kbfiles extension is enabled.

link|flag
The "Case FC2033270" link that you added goes to some generic meta.stackoverflow.com site... is that expected? – Aras Pranckevičius Mar 28 2011 at 7:33
@Aras Yes, that link enables us (administrators) to track the post here back to a case in our internal FogBugz instance at Fog Creek. – Rob Sobers♦ Mar 28 2011 at 16:28
Disabling kbfiles on the client has helped perf significantly. Would we see similar perf improvements by disabling on the server too? If so how do I do that. I can't find the mercurial.ini on my server. – Darrel Miller Aug 8 at 14:54
1

Hi,

Do we have any idea of what actually is the problem (is there something we can do on our end to work around it) and when it will be fixed?

Na'Tosha

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.