On 9/8/06, Paul Mackerras <paulus@xxxxxxxxx> wrote:
Jon Smirl writes: > gitk takes about a minute to come up on the Mozilla repo when > everything is in cache. It takes about twice as long when things are > cold. It's enough of delay that I don't use the tool. How long does it take for git rev-list --topo-order to produce its first line of output, in the cache-hot case? That is, is it just gitk's graph layout that is taking the time, or is it git rev-list (meaning that gitk needs to stop using --topo-order)?
Cold cache: jonsmirl@jonsmirl:/opt/t1$ time git rev-list --all --topo-order --parents >/dev/null real 0m27.687s user 0m5.672s sys 0m0.560s Hot cache: jonsmirl@jonsmirl:/opt/t1$ time git rev-list --all --topo-order --parents >/dev/null real 0m6.041s user 0m5.768s sys 0m0.276s jonsmirl@jonsmirl:/opt/t1$ I have enough RAM (3GB) that everything fits. Hot cache, 27 seconds to get first line of display in gitk It takes about two minutes get everything loaded into the window and scroll to the head This a 450MB pack, 250K commits, 2M objects. -- Jon Smirl jonsmirl@xxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html