From: Mel Gorman <mgorman@suse.de>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: [MMTests] Sysbench read-only on ext4
Date: Mon, 23 Jul 2012 22:14:44 +0100 [thread overview]
Message-ID: <20120723211444.GB9222@suse.de> (raw)
In-Reply-To: <20120629111932.GA14154@suse.de>
Configuration: global-dhp__io-sysbench-large-ro-ext4
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext4
Benchmarks: sysbench
Summary
=======
Looking better in places than ext3 but still of concern.
Benchmark notes
===============
mkfs was run on system startup. No attempt was made to age it. No
special mkfs or mount options were used.
sysbench is an OLTP-like benchmark. The test type was "complex" and
read-only. The table size was 50,000,000 rows regardless of memory size
but far exceeds the memory size of any of the test machines. sysbench
was chosen because it's a reasonably complex OLTP-like benchmark with
straight-forward prerequisites.
The backing database was postgres.
===========================================================
Machine: arnold
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext4/arnold/comparison.html
Arch: x86
CPUs: 1 socket, 2 threads
Model: Pentium 4
Disk: Single Rotary Disk
===========================================================
sysbench
--------
Generally regresssed.
Swapping for kernels 3.1 and 3.2 is very high.
==========================================================
Machine: hydra
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext4/hydra/comparison.html
Arch: x86-64
CPUs: 1 socket, 4 threads
Model: AMD Phenom II X4 940
Disk: Single Rotary Disk
Status: Ok
==========================================================
sysbench
--------
For low number of clients, this has generally improved.
Swapping in kernel 3.1 was high.
==========================================================
Machine: sandy
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext4/sandy/comparison.html
Arch: x86-64
CPUs: 1 socket, 8 threads
Model: Intel Core i7-2600
Disk: Single Rotary Disk
Status:
==========================================================
Generally this is telling a much better story but this could be because
of the much larger memory size of this machine offsetting some other
regression.
Swapping in 3.1 and 3.2.
--
Mel Gorman
SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: [MMTests] Sysbench read-only on ext4
Date: Mon, 23 Jul 2012 22:14:44 +0100 [thread overview]
Message-ID: <20120723211444.GB9222@suse.de> (raw)
In-Reply-To: <20120629111932.GA14154@suse.de>
Configuration: global-dhp__io-sysbench-large-ro-ext4
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext4
Benchmarks: sysbench
Summary
=======
Looking better in places than ext3 but still of concern.
Benchmark notes
===============
mkfs was run on system startup. No attempt was made to age it. No
special mkfs or mount options were used.
sysbench is an OLTP-like benchmark. The test type was "complex" and
read-only. The table size was 50,000,000 rows regardless of memory size
but far exceeds the memory size of any of the test machines. sysbench
was chosen because it's a reasonably complex OLTP-like benchmark with
straight-forward prerequisites.
The backing database was postgres.
===========================================================
Machine: arnold
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext4/arnold/comparison.html
Arch: x86
CPUs: 1 socket, 2 threads
Model: Pentium 4
Disk: Single Rotary Disk
===========================================================
sysbench
--------
Generally regresssed.
Swapping for kernels 3.1 and 3.2 is very high.
==========================================================
Machine: hydra
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext4/hydra/comparison.html
Arch: x86-64
CPUs: 1 socket, 4 threads
Model: AMD Phenom II X4 940
Disk: Single Rotary Disk
Status: Ok
==========================================================
sysbench
--------
For low number of clients, this has generally improved.
Swapping in kernel 3.1 was high.
==========================================================
Machine: sandy
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext4/sandy/comparison.html
Arch: x86-64
CPUs: 1 socket, 8 threads
Model: Intel Core i7-2600
Disk: Single Rotary Disk
Status:
==========================================================
Generally this is telling a much better story but this could be because
of the much larger memory size of this machine offsetting some other
regression.
Swapping in 3.1 and 3.2.
--
Mel Gorman
SUSE Labs
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-07-23 21:14 UTC|newest]
Thread overview: 108+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 11:32 MMTests 0.04 Mel Gorman
2012-06-20 11:32 ` Mel Gorman
2012-06-29 11:19 ` Mel Gorman
2012-06-29 11:19 ` Mel Gorman
2012-06-29 11:21 ` [MMTests] Page allocator Mel Gorman
2012-06-29 11:21 ` Mel Gorman
2012-06-29 11:22 ` [MMTests] Network performance Mel Gorman
2012-06-29 11:22 ` Mel Gorman
2012-06-29 11:23 ` [MMTests] IO metadata on ext3 Mel Gorman
2012-06-29 11:23 ` Mel Gorman
2012-06-29 11:24 ` [MMTests] IO metadata on ext4 Mel Gorman
2012-06-29 11:24 ` Mel Gorman
2012-06-29 11:25 ` [MMTests] IO metadata on XFS Mel Gorman
2012-06-29 11:25 ` Mel Gorman
2012-06-29 11:25 ` Mel Gorman
2012-07-01 23:54 ` Dave Chinner
2012-07-01 23:54 ` Dave Chinner
2012-07-01 23:54 ` Dave Chinner
2012-07-02 6:32 ` Christoph Hellwig
2012-07-02 6:32 ` Christoph Hellwig
2012-07-02 6:32 ` Christoph Hellwig
2012-07-02 14:32 ` Mel Gorman
2012-07-02 14:32 ` Mel Gorman
2012-07-02 14:32 ` Mel Gorman
2012-07-02 19:35 ` Mel Gorman
2012-07-02 19:35 ` Mel Gorman
2012-07-02 19:35 ` Mel Gorman
2012-07-03 0:19 ` Dave Chinner
2012-07-03 0:19 ` Dave Chinner
2012-07-03 0:19 ` Dave Chinner
2012-07-03 10:59 ` Mel Gorman
2012-07-03 10:59 ` Mel Gorman
2012-07-03 10:59 ` Mel Gorman
2012-07-03 11:44 ` Mel Gorman
2012-07-03 11:44 ` Mel Gorman
2012-07-03 11:44 ` Mel Gorman
2012-07-03 12:31 ` Daniel Vetter
2012-07-03 12:31 ` Daniel Vetter
2012-07-03 12:31 ` Daniel Vetter
2012-07-03 13:08 ` Mel Gorman
2012-07-03 13:08 ` Mel Gorman
2012-07-03 13:08 ` Mel Gorman
2012-07-03 13:28 ` Eugeni Dodonov
2012-07-03 13:28 ` Eugeni Dodonov
2012-07-04 0:47 ` Dave Chinner
2012-07-04 0:47 ` Dave Chinner
2012-07-04 0:47 ` Dave Chinner
2012-07-04 9:51 ` Mel Gorman
2012-07-04 9:51 ` Mel Gorman
2012-07-04 9:51 ` Mel Gorman
2012-07-03 13:04 ` Mel Gorman
2012-07-03 13:04 ` Mel Gorman
2012-07-03 13:04 ` Mel Gorman
2012-07-03 14:04 ` Daniel Vetter
2012-07-03 14:04 ` Daniel Vetter
2012-07-03 14:04 ` Daniel Vetter
2012-07-02 13:30 ` Mel Gorman
2012-07-02 13:30 ` Mel Gorman
2012-07-02 13:30 ` Mel Gorman
2012-07-04 15:52 ` [MMTests] Page reclaim performance on ext3 Mel Gorman
2012-07-04 15:52 ` Mel Gorman
2012-07-04 15:53 ` [MMTests] Page reclaim performance on ext4 Mel Gorman
2012-07-04 15:53 ` Mel Gorman
2012-07-04 15:53 ` [MMTests] Page reclaim performance on xfs Mel Gorman
2012-07-04 15:53 ` Mel Gorman
2012-07-05 14:56 ` [MMTests] Interactivity during IO on ext3 Mel Gorman
2012-07-05 14:56 ` Mel Gorman
2012-07-10 9:49 ` Jan Kara
2012-07-10 9:49 ` Jan Kara
2012-07-10 11:30 ` Mel Gorman
2012-07-10 11:30 ` Mel Gorman
2012-07-05 14:57 ` [MMTests] Interactivity during IO on ext4 Mel Gorman
2012-07-05 14:57 ` Mel Gorman
2012-07-23 21:12 ` [MMTests] Scheduler Mel Gorman
2012-07-23 21:12 ` Mel Gorman
2012-07-23 21:13 ` [MMTests] Sysbench read-only on ext3 Mel Gorman
2012-07-23 21:13 ` Mel Gorman
2012-07-24 2:29 ` Mike Galbraith
2012-07-24 2:29 ` Mike Galbraith
2012-07-24 8:19 ` Mel Gorman
2012-07-24 8:19 ` Mel Gorman
2012-07-24 8:32 ` Mike Galbraith
2012-07-24 8:32 ` Mike Galbraith
2012-07-23 21:14 ` Mel Gorman [this message]
2012-07-23 21:14 ` [MMTests] Sysbench read-only on ext4 Mel Gorman
2012-07-23 21:15 ` [MMTests] Sysbench read-only on xfs Mel Gorman
2012-07-23 21:15 ` Mel Gorman
2012-07-23 21:17 ` [MMTests] memcachetest and parallel IO on ext3 Mel Gorman
2012-07-23 21:17 ` Mel Gorman
2012-07-23 21:19 ` [MMTests] memcachetest and parallel IO on xfs Mel Gorman
2012-07-23 21:19 ` Mel Gorman
2012-07-23 21:20 ` [MMTests] Stress high-order allocations on ext3 Mel Gorman
2012-07-23 21:20 ` Mel Gorman
2012-07-23 21:21 ` [MMTests] dbench4 async " Mel Gorman
2012-07-23 21:21 ` Mel Gorman
2012-08-16 14:52 ` Jan Kara
2012-08-16 14:52 ` Jan Kara
2012-08-21 22:00 ` Jan Kara
2012-08-21 22:00 ` Jan Kara
2012-08-22 10:48 ` Mel Gorman
2012-08-22 10:48 ` Mel Gorman
2012-07-23 21:23 ` [MMTests] dbench4 async on ext4 Mel Gorman
2012-07-23 21:23 ` Mel Gorman
2012-07-23 21:24 ` [MMTests] Threaded IO Performance on ext3 Mel Gorman
2012-07-23 21:24 ` Mel Gorman
2012-07-23 21:25 ` [MMTests] Threaded IO Performance on xfs Mel Gorman
2012-07-23 21:25 ` Mel Gorman
2012-07-23 21:25 ` Mel Gorman
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=20120723211444.GB9222@suse.de \
--to=mgorman@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.