mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cliff White <cliffw@osdl.org>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OSDL][BENCHMARK] OSDL-DBT-2 - 2.4 vs 2.5 4-way/8-way with vmstat
Date: Fri, 31 Jan 2003 14:47:59 -0800	[thread overview]
Message-ID: <200301312247.h0VMlxB09932@mail.osdl.org> (raw)
In-Reply-To: Message from Andrew Morton <akpm@digeo.com>  of "Fri, 31 Jan 2003 14:13:50 PST." <20030131141350.370c287a.akpm@digeo.com>

> 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


       reply	other threads:[~2003-01-31 22:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030131141350.370c287a.akpm@digeo.com>
2003-01-31 22:47 ` Cliff White [this message]
2003-01-31 22:57   ` Andrew Morton
2003-01-31 20:26 Cliff White
2003-01-31 21:29 ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200301312247.h0VMlxB09932@mail.osdl.org \
    --to=cliffw@osdl.org \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®