From: Helge Hafting <helgehaf@idb.hist.no>
To: Chris Schanzle <chris.schanzle@jhuapl.edu>, linux-kernel@vger.kernel.org
Subject: Re: I/O causes performance problem with 2.4.8-ac3
Date: Fri, 17 Aug 2001 12:02:58 +0200 [thread overview]
Message-ID: <3B7CEBD2.D3ED4D56@idb.hist.no> (raw)
In-Reply-To: <3B7C08D4.9070303@jhuapl.edu>
Chris Schanzle wrote:
>
> This probably belongs in the "use-once" thread...
>
> I ran into a significant (lack of) performance situation with 2.4.8-ac3
> that does not exist with 2.4.8. Perhaps someone can shed some light on
> what happened and how to avoid it in the future.
[...]
> In other words, system had
> cached a bunch of buffers.
>
> Performance was excellent until I decided to "dd bs=1024k </dev/cdrom
> >somefile" a 600+MB cdrom while a kernel build was going on. It took
[...]
Such a big copy operation is exactly what "use-once" does well.
2.4.8 has use-once, 2.4.8ac3 don't have use-once.
One can construct scenarios where use-once performs worse too,
I believe this is why Alan Cox didn't want it yet.
A big copy without use-once will push everything else out of
cache, and push a lot of programs into swap in order to cache
a lot of the big copy. That's bad if the big
copy is done once and you don't really need the stuff again.
Then you want the "other" stuff to stay in cache instead.
Use-once may perform worse if stuff falls out of cache
and has to be re-read from disk.
Helge Hafting
next prev parent reply other threads:[~2001-08-17 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 17:54 I/O causes performance problem with 2.4.8-ac3 Chris Schanzle
2001-08-17 10:02 ` Helge Hafting [this message]
2001-08-17 17:50 ` Chris Mason
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=3B7CEBD2.D3ED4D56@idb.hist.no \
--to=helgehaf@idb.hist.no \
--cc=chris.schanzle@jhuapl.edu \
--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