Thu, 15 Dec 2011 16:23:26 +0100 largefiles: optimize status when files are specified (issue3144)
Na'Tosha Bard <natosha@unity3d.com> [Thu, 15 Dec 2011 16:23:26 +0100] rev 15653
largefiles: optimize status when files are specified (issue3144) This fixes a performance issue with 'hg status' when files are specified on the command-line. Previously, a large amount of largefiles code was executed, even if files were specified on the command-line and those files were not largefiles. This patch fixes the problem by first checking if non-largefiles were specified on the command-line and, just letting the normal status function handle the case if they were. On a brand new machine, the execution time for 'hg status filename' on a repository with largefiles was: real 0m0.636s user 0m0.512s sys 0m0.120s versus the following (the same repository, with largefiles disabled): real 0m0.215s user 0m0.180s sys 0m0.032s After this patch, the performance of 'hg status filename' on the same repository, with largefiles enabled is: real 0m0.228s user 0m0.189s sys 0m0.036s This performance boost is also true when patterns (rather than specific files) are specified on the command-line. In the case where patterns are specified in addition to a file list, we just defer to the normal codepath in order to not spend extra time expanding the patterns to just risk having to expand them again later.
Mon, 12 Dec 2011 15:16:58 +0100 wireproto: handle other server output in pushkey
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 12 Dec 2011 15:16:58 +0100] rev 15652
wireproto: handle other server output in pushkey Remote side may add useful information alongside failure return code. For example "ssl is required". This patch mirror what is done for the unbundle command.
Thu, 15 Dec 2011 11:45:01 +0100 phases: exchange phase boundaries on push
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 15 Dec 2011 11:45:01 +0100] rev 15651
phases: exchange phase boundaries on push For now phase sync is tried even if push fails with some know pathological case. The exact behavior is to be discussed and implemented later.
(0) -10000 -3000 -1000 -300 -100 -30 -10 -3 +3 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip