Mirror of https://github.com/git/git

Paul Mackerras 466e4fdd66 Only do an update every 100 commits when drawing the graph. ... On a large repository with > 60,000 commits, each call to the Tk update primitive (which gives Tk a chance to respond to events and redraw the screen) was taking up to 0.2 seconds. Because the logic was to call update after drawing a commit if 0.1 seconds had passed since the last update call, we were calling it for every commit, which was slowing us down enormously. Now we also require that we have drawn 100 commits since the last update (as well as it being at least 0.1 seconds since the last update). Drawing 100 commits takes around 0.1 - 0.2 seconds (even in this large repo) on my G5.		2005-08-10 22:50:28 +10:00
gitk	Only do an update every 100 commits when drawing the graph.	2005-08-10 22:50:28 +10:00