On 9/10/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. I've been doing some timing measurements with Jon's repo. The results are interesting.
Using the Mozilla repo you downloaded is not a normal situation since it is 100% packed. Most people are going to have a few thousand loose objects floating around too. Loose objects really slow things down. You noticed too that forks of small apps are relatively slow. The first pass of the import tools used fork for everything and took a week to run with 60% of the time spent in the kernel. There may be some work to do on fork in the kernel. Does mapping the kernel into the top 1G slow down fork of these small apps? Or are they dynamically linked to something that is bringing in millions of pages? When I was doing oprofile all of the time was in the actual fork call and page table copying. -- 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