Thanks for the heads up. Must be falling asleep to miss that one. The run
seems to have progressed ok but something died in the output (Aggelos?).
After deleting that result (just in case) the results look like this:
2.5.58 3 96 82.3 9 5.2 1.22
2.5.58-mm1 3 100 81.0 6 6.0 1.27
>
> >list_load:
> >Kernel [runs] Time CPU% Loads LCPU% Ratio
> >2.5.55 3 91 84.6 0 8.8 1.17
> >2.5.56 3 91 84.6 0 8.8 1.15
> >2.5.57 3 91 84.6 0 8.8 1.15
> >2.5.58 3 91 85.7 0 8.8 1.15
> >2.5.58-mm1 2 92 83.7 0 9.8 1.16
> >mem_load:
> >Kernel [runs] Time CPU% Loads LCPU% Ratio
> >2.5.55 3 116 73.3 66 1.7 1.49
> >2.5.56 3 107 80.4 45 0.9 1.35
> >2.5.57 3 110 80.0 47 0.9 1.39
> >2.5.58 3 107 73.8 66 1.9 1.35
> >2.5.58-mm1 3 104 75.0 50 1.0 1.32
> >dbench_load:
> >Kernel [runs] Time CPU% Loads LCPU% Ratio
> >2.5.55 3 117 68.4 2 16.2 1.50
> >2.5.56 2 124 62.9 3 25.8 1.57
> >2.5.57 3 121 64.5 3 22.3 1.53
> >2.5.58 3 122 64.8 3 24.6 1.54
> >2.5.58-mm1 3 118 66.9 3 22.0 1.49
> >
> >Only statistically significant diff b/w 2.5.58 and 2.5.58-mm1 is in
> > ctar_load which is faster in mm1. Trend towards being faster in mem_load.
> >
> >Con
>
> Looks good, thanks.
No problem.
Will have to keep an eye out on the code for more bugs. So far the contest
code changeover is showing far less variability in the results (good job
Aggelos!) which should make for more meaningful results.
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/