That is what we are trying to do with setting it up on STP. So you
don't have to be a database guy. :-) I guess what we need to explore
is how to change the setup of dbt{123} on STP so that it gives you
the information that you need.
Tim
>
> > > So either the I/O scheduler is doing a better job, or the VM page
> > > replacement decisions are agreeable for this load.
> >
> > Okay. Is there something we could do that would point at one or the other?
>
> Different combinations of working set and physical memory will tell us.
>
> Also, when we have a lot of vmstat/etc traces available we can decide how I/O
> bound it is, and whether we need to look at upping the request queue sizes.
> Which is something which we can now do, and which could easily make a
> difference here.
>
> But we'll have to get you onto at least 2.5.58 for that ;)
>
> > would a smaller memory database (say 2GB instead of 4GB ) really show you
> > anything interesting on a 4GB system, since there's so little pressure?
>
> Yes, that would be interesting. We're dealing with single points in
> twenty-seven-dimensional space. Tweaking input parameter individually helps
> one gain an understanding of what is going on.
> -
> 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/
-- Timothy D. Witham - Lab Director - wookie@osdlab.org Open Source Development Lab Inc - A non-profit corporation 15275 SW Koll Parkway - Suite H - Beaverton OR, 97006 (503)-626-2455 x11 (office) (503)-702-2871 (cell) (503)-626-2436 (fax)- 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/