comparison mercurial/configitems.py @ 40400:db0dba2d157d

profiling: move default mode to "real" time Mercurial operations involve a lot of disks or network access. These impact command runtime significantly and it seems important to report them in our default profiling output. Having the right default means that we don't forget them when asking people to produces profiling traces or when doing profiling ourselves. Moving to "real time" by default will remove the need to think about activating it on most occasions. The "CPU" time-based profiling is still accessible when necessary.
author Boris Feld <boris.feld@octobus.net>
date Sat, 18 Aug 2018 01:44:38 +0200
parents af62936c2508
children 89703e6151e7 ab09e797fbed
comparison
equal deleted inserted replaced
40399:4ab6e7b4fe8a 40400:db0dba2d157d
921 ) 921 )
922 coreconfigitem('profiling', 'statformat', 922 coreconfigitem('profiling', 'statformat',
923 default='hotpath', 923 default='hotpath',
924 ) 924 )
925 coreconfigitem('profiling', 'time-track', 925 coreconfigitem('profiling', 'time-track',
926 default='cpu', 926 default='real',
927 ) 927 )
928 coreconfigitem('profiling', 'type', 928 coreconfigitem('profiling', 'type',
929 default='stat', 929 default='stat',
930 ) 930 )
931 coreconfigitem('progress', 'assume-tty', 931 coreconfigitem('progress', 'assume-tty',