Messages in this thread | | | Date | Fri, 14 Nov 2003 13:12:35 +1100 | From | Nick Piggin <> | Subject | Re: Nick's scheduler v18 |
| |
Martin J. Bligh wrote:
>>Average of 5 kernel compiles (make -j) on a 16-way 512KB cache NUMAQ gives >> bk14 bk14-v18 >>real 83.5s 81.7s >>user 987.6s 992.5s >>sys 158.0s 142.3s >> >>Volanomark looks much better than mainline. >> >>More testing welcome. >> > >-noint is just backing out the interactivity patch (part of your patch) >Not sure that's helping you much really, but maybe it conflicts with >your other stuff. > >Kernbench: (make -j N vmlinux, where N = 2 x num_cpus) > Elapsed System User CPU > 2.6.0-test9 45.28 100.19 568.01 1474.75 > 2.6.0-test9-noint 48.20 99.05 567.26 1389.00 > 2.6.0-test9-nick18 45.06 91.56 568.77 1467.50 > >Kernbench: (make -j N vmlinux, where N = 16 x num_cpus) > Elapsed System User CPU > 2.6.0-test9 46.17 122.20 571.58 1501.00 > 2.6.0-test9-noint 46.43 117.96 577.60 1498.00 > 2.6.0-test9-nick18 46.90 109.05 589.77 1488.75 > >Kernbench: (make -j vmlinux, maximal tasks) > Elapsed System User CPU > 2.6.0-test9 45.84 120.14 570.93 1507.00 > 2.6.0-test9-noint 47.42 123.52 582.91 1488.75 > 2.6.0-test9-nick18 46.83 110.70 588.91 1494.00 > >It seems that you're decreasing system time significantly, but increasing >user time if you have lots of tasks ... context switch thrash, maybe? >
OK, thanks for testing. Still not great.
My patchset does a _lot_ less SMP and NUMA balancing, although I think that sometimes causes too much idle time. It might be doing more context switching though.
> >Would be interesting if you know which of the many patches in there make >the performance difference ... the whole thing is a bit too big to pick >up and maintain easily ;-) >
Its not well broken out though unfortunately. I really need to document and comment it better.
- 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/
| |