From: Andrew Morton <akpm@digeo.com>
To: Cliff White <cliffw@osdl.org>
Cc: cliffw@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [OSDL][BENCHMARK] Database results 2.4 versus 2.5
Date: Fri, 17 Jan 2003 13:37:18 -0800 [thread overview]
Message-ID: <20030117133718.36df6e42.akpm@digeo.com> (raw)
In-Reply-To: <200301172123.h0HLNBd19275@mail.osdl.org>
Cliff White <cliffw@osdl.org> wrote:
>
> > So it sounds like DBT2 is stabilised now, and producing repeatable results?
> > That's excellent.
> Thanks. the kit's available off Sourceforge now, and we'll have STP version
> up Mondayish.
OK. My utter database ignorance was an
insurmountable-within-two-hour-attention-span problem when I tried to set up
dbt1.
> > 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.
next prev parent reply other threads:[~2003-01-17 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 19:21 Cliff White
2003-01-17 21:00 ` Andrew Morton
2003-01-17 21:23 ` Cliff White
2003-01-17 21:37 ` Andrew Morton [this message]
2003-01-17 22:11 ` Timothy D. Witham
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=20030117133718.36df6e42.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=cliffw@osdl.org \
--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®