Re: 2.6.21-rc3-mm1 RSDL results

Con Kolivas
2007-03-10T02:20:44Z

On Saturday 10 March 2007 12:42, Matt Mackall wrote:
> On Sat, Mar 10, 2007 at 12:28:38PM +1100, Con Kolivas wrote:
> > On Saturday 10 March 2007 11:49, Matt Mackall wrote:
> > > On Sat, Mar 10, 2007 at 11:34:26AM +1100, Con Kolivas wrote:
> > > > Ok, so some of the basics then. Can you please give me the output of
> > > > 'top -b' running for a few seconds during the whole affair?
> > >
> > > Here you go:
> > >
> > > http://selenic.com/baseline
> > > http://selenic.com/underload
> > >
> > > This is with 2.6.20+rsdl+tickfix at HZ=250.
> > >
> > > Something I haven't mentioned about my setup is that I'm using ccache.
> > > And it turns out disabling ccache makes a large difference. Going to
> > > switch back to a NO_HZ kernel and see what that looks like.
> >
> > Your X is reniced to -10 so.... try again with X nice 0 please.
>
> Doh, can't believe I didn't notice that. That's apparently a default
> in Debian/unstable (not sure where to tweak it).

See other email from Kyle on how to dpkg reconfigure. I submitted a bug report
to debian years ago about this and I presume it was fixed but you've probably
slowly dist upgraded from an older version and it stayed in your config?

> Reniced:
>
> without ccache with ccache
> make -j 5
> beryl good ok
> galeon ok/good ok
> mp3 good good
> terminal good ok
> mouse good ok

Progress at last! And without any patches! Well those look very reasonable to
me. Especially since -j5 is a worst case scenario.

> We're still left with a big unexplained ccache differential,

But would you say it's still _adequate_ with ccache considering you only have
1/6th cpu left for X? With and without ccache it's quite a different workload
so they will behave differently.

> and a big
> NO_HZ vs HZ=250 differential.

That part I don't know about. You've only tested the difference with X running
nice -10. I need to look further at the mechanism for -nice tasks. It should
be possible to run smoothly even with a -niced X (although that was never my
intent) so perhaps that's not working properly. I'll look into that.

Thanks!

--
-ck