From: Andrew Morton <akpm@linux-foundation.org>
To: hamid.jahanjou@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VM: Implements the swap-out page-clustering technique
Date: Thu, 4 Sep 2008 23:58:35 -0700 [thread overview]
Message-ID: <20080904235835.4406970a.akpm@linux-foundation.org> (raw)
In-Reply-To: <48C0E383.5060308@gmail.com>
On Fri, 05 Sep 2008 11:15:07 +0330 "Hamid R. Jahanjou" <hamid.jahanjou@gmail.com> wrote:
> Andrew Morton wrote:
> > I tried that once. The code all worked as-designed but didn't seem to
> > improve performance much across a spread of workloads.
> >
> > Benchmarks are essential, please. Good ones.
> Do you recommend any specific benchmarks for memory-related projects ?
> Which
> one did you use for your own implementation ?
>
Pretty much any and all benchmarks, when there's not enough memory
(boot with mem=). Kernel compiles, database benchmarks, you name it.
Basically anything which has a measurable execution time is relevant.
Designing and running these things is a lot of work and thought. And
it's an integral part of the development process, because some things
are going to get slower and others will show large inter-run variations
and then one needs to get in there and find explanations and hopefully
fixes.
For example, start with small and simple microbenchmarks: run two
processes which concurrently allocate 1*mem, then modify it all
linearly, then read it all linearly. Build up from there. Do not
dive into complex benchmarks on day 1, because you'll have no hope of
explaining the results which they produce.
Beware that behaviour on SMP can be very different from behaviour on
uniprocessor because of the relatively large duration of a timeslice.
Both must be tested.
next prev parent reply other threads:[~2008-09-05 6:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 12:04 [PATCH] VM: Implements the swap-out page-clustering technique Hamid R. Jahanjou
2008-09-04 23:14 ` Rik van Riel
2008-09-04 23:14 ` Andrew Morton
2008-09-05 7:45 ` Hamid R. Jahanjou
2008-09-05 6:58 ` Andrew Morton [this message]
2008-09-05 9:19 ` Andi Kleen
2008-09-05 20:27 ` Hamid R. Jahanjou
2008-09-05 19:45 ` Andi Kleen
2008-09-06 5:42 ` Rik van Riel
2008-09-08 0:28 ` Zan Lynx
2008-09-08 0:55 ` Rik van Riel
2008-09-10 8:16 ` Hamid R. Jahanjou
2008-09-10 17:08 ` Ray Lee
2008-09-10 17:39 ` Rik van Riel
2008-09-08 3:50 ` Li Yu
2008-09-08 9:51 ` hamidreza jahanjou
[not found] ` <48C4FECF.2000708@gmail.com>
2008-09-08 10:31 ` Li Yu
2008-09-24 13:56 ` Luiz Fernando N. Capitulino
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=20080904235835.4406970a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hamid.jahanjou@gmail.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