From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: riel@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Followup: [PATCH -mm] make swapin readahead skip over holes
Date: Mon, 16 Apr 2012 11:34:12 -0700 (PDT) [thread overview]
Message-ID: <7297ae3b-f3e1-480b-838f-69b0e09a733d@default> (raw)
Hi Rik --
I saw this patch in 3.4-rc1 (because it caused a minor merge
conflict with frontswap) and wondered about its impact.
Since I had a server still set up from running benchmarks
before LSFMM, I ran my kernel compile -jN workload (with
N varying from 4 to 40) on 1GB of RAM, on 3.4-rc2 both with
and without this patch.
For values of N=24 and N=28, your patch made the workload
run 4-9% percent faster. For N=16 and N=20, it was 5-10%
slower. And for N=36 and N=40, it was 30%-40% slower!
Is this expected? Since the swap "disk" is a partition
on the one active drive, maybe the advantage is lost due
to contention?
Thanks,
Dan
commit removed 67f96aa252e606cdf6c3cf1032952ec207ec0cf0
Workload:
kernel compile "make -jN" with varying N
measurements in elapsed seconds
boot kernel: 3.4-rc2
Oracle Linux 6 distro with ext4
fresh reboot for each test run
all tests run as root in multi-user mode
Hardware:
Dell Optiplex 790 = ~$500
Intel Core i5-2400 @ 3.10 GHz, 4coreX2thread, 6M cache
1GB RAM DDR3 1333Mhz (to force swapping)
One 7200rpm SATA 6.0Gb/s drive with 8MB cache
10GB swap partition
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2012-04-16 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 18:34 Dan Magenheimer [this message]
2012-04-16 20:13 ` Rik van Riel
2012-04-17 15:20 ` Dan Magenheimer
2012-04-17 19:26 ` Rik van Riel
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=7297ae3b-f3e1-480b-838f-69b0e09a733d@default \
--to=dan.magenheimer@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/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