Peter Memishian <peter.memish...@sun.com> writes: > While I generally try to limit my use of "hg log" to focused queries > (e.g., -k <bugid>), there are times when I need to dig through the history > with "hg log | less" to find a specific integration of interest. However, > with hg 1.1.2 on a local clone of onnv-gate this ends up being unusable. > > In particular, the first few pages of output show up in a sluggish-but- > tolerable 10-15 seconds. However, as I page further through the history, > the stalls more than double at each instance: first 45 seconds, then > 1m22s, then 3m04s, etc. During these stalls, prstat shows "hg" on-cpu the > whole time but truss shows little going on (just some periodic examination > of .hg/store/00changelog.d), so I presume it's cpu-bound in an inefficient > algorithm, but I'm unsure how to debug this further (in Python). > > Has anyone else experienced this?
Just 'hg log' or, for instance 'hg log -v'? I haven't seen it with the former, no. The latter does considerably more work, and do behave somewhat as you say. -- Rich _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
