All of lore.kernel.org
 help / color / mirror / Atom feed
From: "François Cami" <stilgar2k@wanadoo.fr>
To: Rik van Riel <riel@conectiva.com.br>
Cc: James A Sutherland <jas88@cam.ac.uk>, war <war@starband.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Swap vs No Swap.
Date: Thu, 22 Nov 2001 19:56:02 +0100	[thread overview]
Message-ID: <3BFD4A42.8090002@wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111221456020.1491-100000@duckman.distro.conectiva>

Rik van Riel wrote:

> On Thu, 22 Nov 2001, James A Sutherland wrote:
>>Obviously, there are cases where removing swap breaks the system
>>entirely, but even in other cases, adding swap should *never* degrade
>>performance. (In theory, anyway; in practice, it still needs
>>tuning...)
>>
> 
> Not quite true.  The VM cannot look into the future, so if
> you have swap it could have just swapped out the application
> on the desktop you're about to switch to ;)


I tend to agree. Especially since in some cases (i.e. after
a long compilation (read : lots of code)), the VM has the most
excellent idea to swap out all the GUI (X+apps) and everyone
here knows how long it can be to restore the GUI in that case.

Obviously the problem is very much lessened, in my case, when
i put the swap partition on the *other* drive than the root fs.
Both are ATA100 (40GB 60GXPs), and the system is more responsive
with swap on hdc while / in on hda, than both on hda.

François


  reply	other threads:[~2001-11-22 18:52 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22  1:53 Swap vs No Swap war
2001-11-22  2:23 ` Joel Jaeggli
2001-11-22  2:31   ` war
2001-11-22  2:58 ` Mark Hahn
2001-11-22  4:09 ` listmail
2001-11-22  5:24 ` H. Peter Anvin
2001-11-22  5:30   ` war
2001-11-22  5:32     ` H. Peter Anvin
2001-11-22  9:50       ` Christian Bornträger
2001-11-22  8:50 ` Rik van Riel
2001-11-22 11:00 ` James A Sutherland
2001-11-22 16:00   ` war
2001-11-22 16:08     ` James A Sutherland
2001-11-22 16:57       ` Rik van Riel
2001-11-22 18:56         ` François Cami [this message]
2001-11-22 18:58           ` James A Sutherland
2001-11-22 19:17             ` François Cami
2001-11-22 19:36               ` G . Sumner Hayes
2001-11-22 20:37                 ` James A Sutherland
2001-11-23  6:30       ` Charles Marslett
2001-11-23  9:13         ` James A Sutherland
2001-11-23 16:46           ` Charles Marslett
2001-11-22 16:25   ` war
2001-11-22 16:37     ` Ryan Cumming
2001-11-22 17:39     ` James A Sutherland
2001-11-22 17:56       ` war
     [not found] ` <01112211150302.00690@argo>
2001-11-22 16:01   ` war
2001-11-22 16:12     ` James A Sutherland
2001-11-22 16:36       ` war
2001-11-22 16:33         ` Bjorn Wesen
2001-11-22 17:37         ` Thomas S. Iversen
2001-11-22 21:18           ` Mike Galbraith
2001-11-22 17:41         ` James A Sutherland
2001-11-22 17:56           ` war
2001-11-22 18:08             ` James A Sutherland
2001-11-23 22:05       ` Daniel Gryniewicz
  -- strict thread matches above, loose matches on Subject: below --
2001-11-22 16:11 Elgar, Jeremy
2001-11-22 16:22 ` Ryan Cumming
2001-11-22 16:22 ` Stephan von Krawczynski
2001-11-22 16:29 Elgar, Jeremy
     [not found] <Pine.LNX.4.10.10111221006010.29736-100000@coffee.psychology.mcmaster.ca>
2001-11-22 16:34 ` war
2001-11-26 20:18   ` Kent Borg

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=3BFD4A42.8090002@wanadoo.fr \
    --to=stilgar2k@wanadoo.fr \
    --cc=jas88@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=war@starband.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 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.