All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Benjamin Rutt <rutt.4+news@osu.edu>, linux-kernel@vger.kernel.org
Subject: Re: clearing filesystem cache for I/O benchmarks
Date: Tue, 27 Jul 2004 00:16:14 -0700	[thread overview]
Message-ID: <4106013E.30408@namesys.com> (raw)
In-Reply-To: <20040726234005.597a94db.akpm@osdl.org>

Andrew Morton wrote:

>(Please don't remove people from the email recipient list when doing kernel
>work.)
>
>Benjamin Rutt <rutt.4+news@osu.edu> wrote:
>  
>
>>Andrew Morton <akpm@osdl.org> writes:
>>
>>    
>>
>>>Benjamin Rutt <rutt.4+news@osu.edu> wrote:
>>>      
>>>
>>>> How can I purge all of the kernel's filesystem caches, so I can trust
>>>> that my I/O (read) requests I'm trying to benchmark bypass the kernel
>>>> filesystem cache?
>>>>        
>>>>
>>>Either delete the benchmark test files or
>>>      
>>>
>>I'm not sure I follow.  If I delete the benchmark files, I'll only
>>need to create them again later in order to do a read test, and I'll
>>have the same problem then, of how to eliminate the just-written-data
>>from cache.
>>    
>>
when benchmarking, please be careful that you don't end up benchmarking 
umount/mount, or sync, or..... it can be remarkably hard to avoid such 
mistakes.....

I tend to try to use large enough filesets that small things like cache 
flush happenstance or bitmap loading overhead do not sway the benchmark.

Rebooting tends to work for resetting the OS thoroughly, though I would 
be curious to hear comments on whether one ought to power down the disk 
drive so that its cache flushes......;-)



  reply	other threads:[~2004-07-27  7:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 22:54 clearing filesystem cache for I/O benchmarks Benjamin Rutt
2004-07-24  5:21 ` Chris Wedgwood
2004-07-24  5:31 ` Tim Wright
2004-07-26  0:07   ` Benjamin Rutt
2004-07-26  1:40     ` Bernd Eckenfels
2004-07-26 12:47       ` Benjamin Rutt
2004-07-25  8:11 ` Andreas Haumer
2004-07-26  7:25 ` Andrew Morton
2004-07-26 13:02   ` Benjamin Rutt
2004-07-27  6:40     ` Andrew Morton
2004-07-27  7:16       ` Hans Reiser [this message]
2004-07-27 17:31         ` Benjamin Rutt
2004-07-27 18:03           ` Hans Reiser
2004-07-28 12:38             ` Benjamin Rutt
2004-07-28 17:03               ` Hans Reiser
2004-07-28 18:19                 ` Benjamin Rutt
2004-07-27 17:25       ` Benjamin Rutt
2004-07-27 20:00         ` Timothy Miller
2004-07-28 12:51           ` Benjamin Rutt
2004-07-29  1:05       ` Nathan Scott

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=4106013E.30408@namesys.com \
    --to=reiser@namesys.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rutt.4+news@osu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.