Messages in this thread | | | Date | Tue, 4 Mar 2003 00:10:32 -0800 | From | Andrew Morton <> | Subject | Re: [BENCHMARK] 2.5.63-mm2 + i/o schedulers with contest |
| |
Con Kolivas <kernel@kolivas.org> wrote: > > Mem_load result of AS being slower was just plain weird with the result rising > from 100 to 150 during testing. >
Maybe we should just swap computers or something?
Finished compiling kernel: elapsed: 145 user: 180 system: 18 Finished mem_load: elapsed: 146 user: 0 system: 2 loads: 5000 Finished compiling kernel: elapsed: 135 user: 181 system: 17 Finished mem_load: elapsed: 136 user: 0 system: 2 loads: 4800 Finished compiling kernel: elapsed: 129 user: 181 system: 17 Finished mem_load: elapsed: 130 user: 0 system: 2 loads: 4800
256MB, dual CPU, ext3/IDE.
Whereas 2.5.63+bk gives:
Finished compiling kernel: elapsed: 131 user: 182 system: 17 Finished mem_load: elapsed: 131 user: 0 system: 1 loads: 4900 Finished compiling kernel: elapsed: 135 user: 182 system: 17 Finished mem_load: elapsed: 135 user: 0 system: 1 loads: 4800 Finished compiling kernel: elapsed: 129 user: 182 system: 17 Finished mem_load: elapsed: 129 user: 0 system: 1 loads: 4600
Conceivably swap fragmentation, but unlikely. Is it still doing a swapoff between runs? - 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/
| |