Quoting Con Kolivas <conman@kolivas.net>:
> I've been trialling a new load module for the contest benchmark
> (http://contest.kolivas.net) which simply forks a process that just exits
> waits for it to die, then repeats. Here are the results I have obtained so
> far:
>
[...fresh results below...]
> ck7 uses O1, preempt, low latency
> Preempt=N for all other kernels
>
> Clearly you can see the 2.5 kernels have a substantial lead over the
> current
> stable kernel.
>
> This load module is not part of the contest package yet. I could certainly
> change it to fork n processes but I'm not really sure just how many n should
> be.
I have extra information from the trial of this module:
noload:
Kernel Time CPU Ratio
2.4.19 72.90 99% 1.00
2.4.19-ck7 71.55 100% 0.98
2.5.38 73.86 99% 1.01
2.5.38-mm2 73.93 99% 1.01
fork_load:
Kernel Time CPU Ratio
2.4.19 97.11 67% 1.33
2.4.19-ck7 72.34 92% 0.99
2.5.38 75.32 92% 1.03
2.5.38-mm2 74.99 92% 1.03
2.4.19: Children forked: 32750
2.4.19-ck7: Children forked: 6477
2.5.38: Children forked: 5545
2.5.38-mm2: Children forked: 5351
You can see clearly repeatedly forking a new process significantly slows down
compile time for 2.4.19 but not the O(1) based kernels. However, the number of
processes that are forked is significantly reduced.
Is this information useful?
Con
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Sep 30 2002 - 22:00:25 EST