From: Helge Hafting <helgehaf@aitel.hist.no>
To: rmoser <mlmoser@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How do I make this thing stop laging? Reboot? Sounds like Windows!
Date: Wed, 18 Jun 2003 10:22:34 +0200 [thread overview]
Message-ID: <3EF0214A.3000103@aitel.hist.no> (raw)
In-Reply-To: <200306172030230870.01C9900F@smtp.comcast.net>
rmoser wrote:
[...]
> Ten minutes later I get the brains to run top. It seems I have about
> 50 MB in swap, and 54 MB free memory. So I wait ten minutes more.
>
> No change.
>
> % swapoff -a; swapon -a
>
> Fixes all my problems.
>
> Now this long story shows something: The kernel appears to be unable
> to intelligently pull swap back into RAM. What gives?
>
Because the problem _is_ unsolvable. You want the kernel
to go "oh, lots of free memory showed up, lets pull
everything in from swap just in case someone might need it."
That would solve _your_ problem. But lots of other people
would get another problem - much _more_ swapping:
Whenever they quit one big app to run another big one,
everything is pulled in from swap before the next
big app start. Then it starts, and push everything out
again. The current system lets you quit one app,
the stuff in swap remains there until someone actually use it,
and lots of free memory remain in case it is needed.
The "intelligent" thing is to leave stuff in swap until
some app needs it, and pull it in then. Perhaps with
some read-ahead/clustering to minimize io load.
It is simply impossible to know "what" the
next thing we will need from swap will be, and what
stuff won't ever be needed from swap. The memory
might be putr to better uses, such as:
1. New programs/allocations can start without
having to push something out first
2. file cache for io-intensive apps.
Note that reading from swap is very much like reading
from executable files - it is done when needed.
We donæ't normally pre-read every executable
on the system when there is free memory just
in case someone might want to run a program,
the same applies to swap.
Helge Hafting
next prev parent reply other threads:[~2003-06-18 8:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 0:30 rmoser
2003-06-18 8:22 ` Helge Hafting [this message]
2003-06-18 9:22 ` Karl Vogel
2003-06-18 9:44 ` Oliver Neukum
2003-06-18 10:23 ` Anders Karlsson
2003-06-18 15:08 ` Gianni Tedesco
2003-06-18 16:43 ` Joe
2003-06-18 9:30 ` Yaroslav Rastrigin
2003-06-18 11:02 ` Helge Hafting
2003-06-18 12:17 ` Mike Galbraith
2003-06-19 8:04 ` H. Peter Anvin
2003-06-19 10:00 ` Helge Hafting
2003-06-19 10:02 ` Nick Piggin
2003-06-19 15:54 ` Daniel Gryniewicz
2003-06-18 9:56 Karl Vogel
2003-06-18 16:53 ` Oliver Neukum
2003-06-18 10:43 Karl Vogel
2003-06-18 10:49 Karl Vogel
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=3EF0214A.3000103@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mlmoser@comcast.net \
/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®