public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Clemens Schwaighofer <cs@tequila.co.jp>
Cc: kernel@kolivas.org, Joel.Becker@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: Autotune swappiness01
Date: Mon, 26 Jul 2004 18:09:43 -0700	[thread overview]
Message-ID: <20040726180943.4c871e4f.akpm@osdl.org> (raw)
In-Reply-To: <4105A761.9090905@tequila.co.jp>

Clemens Schwaighofer <cs@tequila.co.jp> wrote:
>
> Con Kolivas wrote:
> | Andrew Morton writes:
> 
> |> Yes, I think 60% is about right for a 512-768M box.  Too high for the
> |> smaller machines, too low for the larger ones.
> |
> |
> | Sigh..
> | I have a 1Gb desktop machine that refuses to keep my applications in ram
> | overnight if I have a swappiness higher than the default so I think lots
> | of desktop users with more ram will be unhappy with higher settings.
> 
> I have 1 GB and I had a setting of 51 (seemed to be perhaps gentoo
> default or so) and I especially after a weekend (2 days off) it is
> always the "monday-morning-swap-hell" where I have to wait 5min until he
> swapped in the apps he swapped out during weekend.
> 
> I changed that to 20 now, but I don't know if this will make things
> worse or better.
> 

It may appear to be better, but you now have 100, maybe 200 megabytes less
pagecache available across the entire working day.


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

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26  0:25 [PATCH][2.6.8-rc1-mm1] Autotune swappiness01 Con Kolivas
2004-07-26  0:36 ` Andrew Morton
2004-07-26  0:43   ` Con Kolivas
2004-07-26  0:48     ` Andrew Morton
2004-07-26  1:01       ` Con Kolivas
2004-07-26  1:09         ` Con Kolivas
2004-07-26  8:52           ` R. J. Wysocki
2004-07-26  9:31             ` Con Kolivas
2004-07-26 10:34               ` R. J. Wysocki
2004-07-26 10:29                 ` Con Kolivas
2004-07-26 10:54                   ` R. J. Wysocki
2004-07-26 11:03                     ` Con Kolivas
2004-07-26 11:13                       ` Nick Piggin
2004-07-26 11:17                         ` Con Kolivas
2004-07-26 11:47                           ` Nick Piggin
2004-07-26 13:53                             ` R. J. Wysocki
2004-07-26 18:45                               ` Adam Kropelin
2004-07-26 18:53                                 ` R. J. Wysocki
2004-07-26 17:55                     ` Gerrit Huizenga
2004-07-26 20:29     ` Joel Becker
2004-07-26 20:42       ` Andrew Morton
2004-07-26 22:58         ` Con Kolivas
2004-07-27  0:52           ` Clemens Schwaighofer
2004-07-27  1:09             ` Andrew Morton [this message]
2004-07-27  1:17               ` Clemens Schwaighofer
2004-07-27  2:03                 ` Tim Connors
2004-07-27  2:43                   ` Con Kolivas
2004-07-27  3:02                     ` Tim Connors
2004-07-27  3:43                       ` Clemens Schwaighofer
2004-07-27  3:47                       ` Joel Becker
2004-07-27 15:32                         ` William Lee Irwin III
2004-07-27  3:41                   ` Clemens Schwaighofer
  -- strict thread matches above, loose matches on Subject: below --
2004-07-26 14:52 Martin Knoblauch
2004-07-26 21:29 DaMouse

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=20040726180943.4c871e4f.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Joel.Becker@oracle.com \
    --cc=cs@tequila.co.jp \
    --cc=kernel@kolivas.org \
    --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