* Willy Tarreau <[EMAIL PROTECTED]> wrote: > > > I will also need to do more testing on the linux kernel tree. > > > Committing patch-2.6.7 on 2.6.6 kernel and then diffing results in > > > > > > $ time gitdiff.sh `parent-id` `tree-id` >p > > > real 5m37.434s > > > user 1m27.113s > > > sys 2m41.036s > > > > > > which is pretty horrible, it seems to me. Any benchmarking help is of > > > course welcomed, as well as any other feedback. > > > > it seems from the numbers that your system doesnt have enough RAM for > > this and is getting IO-bound? > > Not the only problem, without I/O, he will go down to 4m8s (u+s) which > is still in the same order of magnitude.
probably not the only problem - but if we are lucky then his system was just trashing within the kernel repository and then most of the overhead is the _unnecessary_ IO that happened due to that (which causes CPU overhead just as much). The dominant system time suggests so, to a certain degree. Maybe this is wishful thinking. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/