From: Andy Isaacson <adi@hexapodia.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Buddy Lumpkin <b.lumpkin@attbi.com>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: About the need of a swap area
Date: Tue, 30 Jul 2002 14:31:11 -0500 [thread overview]
Message-ID: <20020730143111.B8157@hexapodia.org> (raw)
In-Reply-To: <1027813211.21516.2.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Sun, Jul 28, 2002 at 12:40:11AM +0100
On Sun, Jul 28, 2002 at 12:40:11AM +0100, Alan Cox wrote:
> On Sat, 2002-07-27 at 23:22, Buddy Lumpkin wrote:
> > I thought linux worked more like Solaris where it didn't use any swap (AT
> > ALL) until it has to... At least, I hope linux works this way.
>
> I'd be suprised if Solaris did something that dumb.
>
> You want to push out old long unaccessed pages of code to make room for
> more cached disk blocks from files.
... unless the disk blocks are coming in due to a sequential stream
that's much larger than memory, in which case paging out user data to
expand the buffer cache is an exercise in futility that makes the system
behave sluggishly long AFTER the stream is done streaming through.
I see this behavior every morning after the nightly backup is done
(pulling in about 20 GB of data on a 256MB machine) -- my window manager
and browser are absurdly sluggish for about 20 seconds.
-andy
next prev parent reply other threads:[~2002-07-30 19:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 12:22 About the need of a swap area DervishD
2002-07-27 14:42 ` Ville Herva
2002-07-27 15:47 ` Rik van Riel
2002-07-27 20:41 ` Buddy Lumpkin
2002-07-27 20:50 ` Rik van Riel
2002-07-27 16:11 ` DervishD
2002-07-27 17:01 ` Ville Herva
2002-07-28 11:04 ` DervishD
2002-07-29 13:14 ` [lkml] " Ian Soboroff
2002-07-28 0:02 ` Denis Vlasenko
2002-07-27 20:58 ` Austin Gonyou
2002-07-27 22:22 ` Buddy Lumpkin
2002-07-27 23:40 ` Alan Cox
2002-07-27 22:35 ` Rik van Riel
2002-07-27 22:49 ` Buddy Lumpkin
2002-07-27 23:36 ` Daniel Phillips
2002-07-27 22:39 ` Buddy Lumpkin
2002-07-28 0:03 ` Alan Cox
2002-07-27 22:52 ` Rik van Riel
2002-07-27 23:01 ` Buddy Lumpkin
2002-07-28 0:28 ` Alan Cox
2002-07-27 23:34 ` Buddy Lumpkin
2002-07-28 6:58 ` Ville Herva
2002-07-28 7:59 ` Buddy Lumpkin
2002-07-28 8:19 ` Ville Herva
2002-07-28 14:11 ` Rik van Riel
2002-07-28 15:57 ` Ville Herva
2002-07-28 18:48 ` Buddy Lumpkin
2002-07-28 18:58 ` Ed Sweetman
2002-07-28 19:29 ` Rik van Riel
2002-07-28 19:47 ` Ed Sweetman
2002-07-28 20:42 ` Buddy Lumpkin
2002-07-28 20:27 ` Ville Herva
2002-07-30 19:31 ` Andy Isaacson [this message]
2002-07-28 16:20 ` Austin Gonyou
2002-07-29 7:18 ` Val Henson
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=20020730143111.B8157@hexapodia.org \
--to=adi@hexapodia.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=b.lumpkin@attbi.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