> Cliff White <cliffw@osdl.org> wrote:
> >
> > http://www.osdl.org/projects/dbt2dev/results/8way/LKML2/data/296/vmstat.out
>
> That's progress, thanks.
>
> It is useful to show the collection interval of vmstat in the reports. Is
> that `vmstat 1' or `vmstat 1000'?
vmstat interval is 60 seconds, you are right, we'll fix the report.
>
> This workload appears to be performing concurrent disk reads and writes. If
> these are _really_ happening at the same time (ie: if vmstat hasn't confused
> me) then it could well be the case that the throughput improvement comes from
> the I/O scheduler's tendency to service reads more promptly when there is a
> lot of writeback happening.
Re concurrent IO:
The offical answer from the dba's: "Well, it tries"
There are multiple user proccessess doing queries and commits.
There should be a difference between the cached and non-cached runs, as
the cached runs should not be doing much writing, except to the log device.
Every 10 minutes in all workloads, the database flushes cache to the
datafiles,
which should produce a noticeable peak in activity.
These loads suck up all the memory they can, so anything that gives us more
free memory should
be goodness. We think we are also seeing improvements in 2.5 in free memory,
but
we don't know for sure where is best to look and how best to prove it.
Any advice?
>
> If so then you can expect to see wild swings in results as you wend your way
> through recent 2.5 kernels :(. I'm working on settling that all down.
> 2.5.59-mm7 should do well.
>
Hopefully we can get some results for you on that kernel.
cliffw
-
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 : Fri Jan 31 2003 - 22:00:26 EST