summaryrefslogtreecommitdiff
path: root/git-whatchanged
diff options
context:
space:
mode:
authorLibravatar Paul Mackerras <paulus@samba.org>2005-08-10 22:50:28 +1000
committerLibravatar Paul Mackerras <paulus@samba.org>2005-08-10 22:50:28 +1000
commit466e4fdd6696c89700294e1a54fa73e1fb94643b (patch)
tree913e53f0b6d45ddc8050a4dce9c685b62a882f74 /git-whatchanged
parent[PATCH] "Child" information in commit window - and cleanups (diff)
downloadtgif-466e4fdd6696c89700294e1a54fa73e1fb94643b.tar.xz
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.
Diffstat (limited to 'git-whatchanged')
0 files changed, 0 insertions, 0 deletions