> noload:
> Kernel [runs] Time CPU% Loads LCPU% Ratio
> 2.4.19-rmap15 [1] 84.6 95 0 0 1.00
> 2.4.19-rmap14c [1] 84.2 96 0 0 1.00
> 2.4.20-rc1aa1 [2] 41.0 49 0 0 inf
The time for rc1aa1 here is obviously wrong - this is a bug in contest,
according to Dr. Kolivas :-)
>
> process_load:
> Kernel [runs] Time CPU% Loads LCPU% Ratio
> 2.4.19-rmap15 [1] 140.8 55 133 45 1.66
> 2.4.19-rmap14c [1] 139.4 56 126 45 1.65
> 2.4.20-rc1aa1 [2] 133.9 14 211 84 inf
>
> io_load:
> Kernel [runs] Time CPU% Loads LCPU% Ratio
> 2.4.19-rmap15 [1] 164.8 51 33 19 1.95
> 2.4.19-rmap14c [1] 160.1 53 33 21 1.90
> 2.4.20-rc1aa1 [1] 166.2 49 44 23 inf
>
> read_load:
> Kernel [runs] Time CPU% Loads LCPU% Ratio
> 2.4.19-rmap15 [1] 0.0 0 0 7 0.00
> 2.4.19-rmap14c [1] 121.0 72 20 7 1.44
> 2.4.20-rc1aa1 [1] 111.2 79 34 14 inf
>
> rmap15 OOM'd the cc1 process twice and fscked this run up.
>
> list_load:
> Kernel [runs] Time CPU% Loads LCPU% Ratio
> 2.4.19-rmap15 [1] 99.2 84 0 7 1.17
> 2.4.19-rmap14c [1] 100.7 83 0 7 1.20
> 2.4.20-rc1aa1 [1] 96.7 85 0 8 inf
>
> mem_load:
> Kernel [runs] Time CPU% Loads LCPU% Ratio
> 2.4.19-rmap15 [1] 111.2 80 96 8 1.31
> 2.4.19-rmap14c [1] 106.1 82 96 9 1.26
> 2.4.20-rc1aa1 [1] 126.3 66 77 3 inf
>
-
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/