Re: [PATCH] O6int for interactivity

From: Nick Piggin (piggin@cyberone.com.au)
Date: Fri Jul 18 2003 - 01:34:24 EST


Mike Galbraith wrote:

> At 03:12 PM 7/16/2003 -0700, Davide Libenzi wrote:
>
>> http://www.xmailserver.org/linux-patches/irman2.c
>>
>> and run it with different -n (number of tasks) and -b (CPU burn ms
>> time).
>> At the same time try to build a kernel for example. Then you will
>> realize
>> that interactivity is not the bigger problem that the scheduler has
>> right
>> now.
>
>
> I added an irman2 load to contest. Con's changes 06+06.1 stomped it
> flat [1]. irman2 is modified to run for 30s at a time, but with
> default parameters.
>
> -Mike
>
> [1] imho a little too flat. it also made a worrisome impression on
> apache bench
>
>
>------------------------------------------------------------------------
>
>no_load:
>Kernel [runs] Time CPU% Loads LCPU% Ratio
>2.5.69 1 153 94.8 0.0 0.0 1.00
>2.5.70 1 153 94.1 0.0 0.0 1.00
>2.6.0-test1 1 153 94.1 0.0 0.0 1.00
>2.6.0-test1-mm1 1 152 94.7 0.0 0.0 1.00
>cacherun:
>Kernel [runs] Time CPU% Loads LCPU% Ratio
>2.5.69 1 146 98.6 0.0 0.0 0.95
>2.5.70 1 146 98.6 0.0 0.0 0.95
>2.6.0-test1 1 146 98.6 0.0 0.0 0.95
>2.6.0-test1-mm1 1 146 98.6 0.0 0.0 0.96
>process_load:
>Kernel [runs] Time CPU% Loads LCPU% Ratio
>2.5.69 1 331 43.8 90.0 55.3 2.16
>2.5.70 1 199 72.4 27.0 25.5 1.30
>2.6.0-test1 1 264 54.5 61.0 44.3 1.73
>2.6.0-test1-mm1 1 323 44.9 88.0 54.2 2.12
>ctar_load:
>Kernel [runs] Time CPU% Loads LCPU% Ratio
>2.5.69 1 190 77.9 0.0 0.0 1.24
>2.5.70 1 186 80.1 0.0 0.0 1.22
>2.6.0-test1 1 213 70.4 0.0 0.0 1.39
>2.6.0-test1-mm1 1 207 72.5 0.0 0.0 1.36
>xtar_load:
>Kernel [runs] Time CPU% Loads LCPU% Ratio
>2.5.69 1 196 75.0 0.0 3.1 1.28
>2.5.70 1 195 75.9 0.0 3.1 1.27
>2.6.0-test1 1 193 76.7 1.0 4.1 1.26
>2.6.0-test1-mm1 1 195 75.9 1.0 4.1 1.28
>io_load:
>Kernel [runs] Time CPU% Loads LCPU% Ratio
>2.5.69 1 437 34.6 69.1 15.1 2.86
>2.5.70 1 401 37.7 72.3 17.4 2.62
>2.6.0-test1 1 243 61.3 48.1 17.3 1.59
>2.6.0-test1-mm1 1 336 44.9 64.5 17.3 2.21
>

Looks like gcc is getting less priority after a read completes.
Keep an eye on this please.

-
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 : Wed Jul 23 2003 - 22:00:32 EST