public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Peloquin <peloquin@austin.ibm.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Nightly regression run results
Date: Fri, 06 Jun 2003 17:38:07 -0500	[thread overview]
Message-ID: <3EE117CF.9060106@austin.ibm.com> (raw)
In-Reply-To: 3EDFEFBB.7080507@cyberone.com.au

Hi Nick,

Yes, the read tests do currently run primarily out of cache. This does 
have some value for measuring the relative overhead of the i/o apis. To 
avoid cache effects, and measure the real throughput, we need to bump 
the size up and, as you suggest, size*2 is a good value to use. We've 
tried to keep the overall test suite time down by maintaining shorter 
runs whereever possible. So rather than increasing to run size by 2, we 
will reduce the memory used, at boot, then use runs of newsmallsize*2. 
This will keep the runs from taking too long and also avoid the cache 
benefits. We will have to tweak this to come up with the appropriate 
balance of memsize vs run time. This should be available in a few days.

Thanks for the feedback.

Mark

Nick Piggin wrote:

>
>
> Mark Peloquin wrote:
>
>>
>>
>> Here are links to some 2.5.70 nightly regression comparisons:
>>
> It appears your tiobench reads are coming out of cache.
> Would you be able add some runs with the size >= 2*ram
> please? I don't know if anyone would still find the
> current type useful - maybe for scalability work?
>
> Thanks
> Nick




  reply	other threads:[~2003-06-06 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05 16:26 Nightly regression run results Mark Peloquin
2003-06-06  1:34 ` Nick Piggin
2003-06-06 22:38   ` Mark Peloquin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-05 18:45 Steven Pratt

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=3EE117CF.9060106@austin.ibm.com \
    --to=peloquin@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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