All of lore.kernel.org
 help / color / mirror / Atom feed
From: deepfire@zelnet.ru
To: linux-kernel@vger.kernel.org
Cc: kernel@kolivas.org, akpm@osdl.org
Subject: Re: Autoregulate swappiness & inactivation
Date: Sat, 01 Jan 2000 18:31:50 +0100	[thread overview]
Message-ID: <200001011731.e01HVoNu001908@altair.deep.net> (raw)


Andrew Morton <akpm@osdl.org> wrote at Thu, 8 Jul 2004 09:44:06 -0700:
> Con Kolivas <kernel@kolivas.org> wrote:
> >
> > Here is another try at providing feedback to tune the vm_swappiness.
> 
> I spent some time yesterday trying to demonstrate performance improvements
> from those two patches.  Using
> 
> 	make -j4 vmlinux with mem=64m
> 
> and
> 
> 	qsbench -p 4 -m 96 with mem=256m
> 
> and was not able to do so, which is what I expected.
> 
> We do need more quantitative testing on this work.

i`ve done some of my favorite under-bridge-crafted tests, so to speak.

the test looked like this:

time find / -xdev | \
bzcat --compress | bzcat --decompress | \
bzcat --compress | bzcat --decompress | \
bzcat --compress | bzcat --decompress | \
cat > /dev/null

The patches applied were Con`s autoswap + autoregulate

it was performed on a p3-600, 10krpm scsi in two following scenarios:


1. mem=48M, swap=off

2.4.20-pre9:		3m20
2.6.7-con:		4m09
2.6.7-vanilla:		4m09


2. mem=32M, swap=on

2.4.20-pre9:		5m37
2.6.7-con:		6m37
2.6.7-vanilla:		7m31



which still leaves 2.4 the leader.


regards, Samium "2.4" Gromoff

             reply	other threads:[~2004-07-09 12:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-01 17:31 deepfire [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-07 15:16 2.6.7-ck5 Con Kolivas
2004-07-07 15:39 ` 2.6.7-ck5 John Richard Moser
2004-07-07 15:47   ` 2.6.7-ck5 Con Kolivas
2004-07-08  4:38     ` 2.6.7-ck5 Andrew Morton
2004-07-08  6:40       ` [PATCH] Autoregulate swappiness & inactivation Con Kolivas
2004-07-08  6:45         ` Con Kolivas
2004-07-08  7:06         ` [PATCH] " Nick Piggin
2004-07-08  7:12           ` Con Kolivas
2004-07-08  7:31             ` Nick Piggin
2004-07-08  8:03               ` Con Kolivas
2004-07-08  8:12                 ` Nick Piggin
2004-07-08 17:06                   ` John Richard Moser
2004-07-08  7:10         ` [PATCH] " Andrew Morton
2004-07-08  7:58           ` Con Kolivas
2004-07-08  8:08             ` Andrew Morton
2004-07-08  8:27               ` Con Kolivas
2004-07-08 10:54                 ` FabF
2004-07-09  1:05                   ` Con Kolivas
2004-07-09  9:48                     ` FabF
2004-07-09 10:43                       ` Nick Piggin
2004-07-09 11:14                         ` FabF
2004-07-09 11:24                           ` Nick Piggin
2004-07-10  9:44                             ` FabF
2004-07-08 16:26                 ` Timothy Miller
2004-07-08 17:12                   ` John Richard Moser
2004-07-08 18:37                     ` Timothy Miller
2004-07-08 21:40                       ` John Richard Moser
2004-07-09  7:44                     ` Felipe Alfaro Solana

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=200001011731.e01HVoNu001908@altair.deep.net \
    --to=deepfire@zelnet.ru \
    --cc=akpm@osdl.org \
    --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 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.