From: Fengguang Wu <fengguang.wu@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Glauber Costa <glommer@parallels.com>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
lkp@linux.intel.com
Subject: Re: [numa shrinker] 9b17c62382: -36.6% regression on sparse file copy
Date: Wed, 8 Jan 2014 19:14:40 +0800 [thread overview]
Message-ID: <20140108111440.GA10467@localhost> (raw)
In-Reply-To: <20140106131042.GA5145@destitution>
On Tue, Jan 07, 2014 at 12:10:42AM +1100, Dave Chinner wrote:
> On Mon, Jan 06, 2014 at 04:20:48PM +0800, fengguang.wu@intel.com wrote:
> > Hi Dave,
> >
> > We noticed throughput drop in test case
> >
> > vm-scalability/300s-lru-file-readtwice (*)
> >
> > between v3.11 and v3.12, and it's still low as of v3.13-rc6:
> >
> > v3.11 v3.12 v3.13-rc6
> > --------------- ------------------------- -------------------------
> > 14934707 ~ 0% -48.8% 7647311 ~ 0% -47.6% 7829487 ~ 0% vm-scalability.throughput
> > ^^ ^^^^^^
> > stddev% change%
>
> What does this vm-scalability.throughput number mean?
It's the total throughput reported by all the 240 dd:
8781176832 bytes (8.8 GB) copied, 299.97 s, 29.3 MB/s
2124931+0 records in
2124930+0 records out
8703713280 bytes (8.7 GB) copied, 299.97 s, 29.0 MB/s
2174078+0 records in
2174077+0 records out
...
> > (*) The test case basically does
> >
> > truncate -s 135080058880 /tmp/vm-scalability.img
> > mkfs.xfs -q /tmp/vm-scalability.img
> > mount -o loop /tmp/vm-scalability.img /tmp/vm-scalability
> >
> > nr_cpu=120
> > for i in $(seq 1 $nr_cpu)
> > do
> > sparse_file=/tmp/vm-scalability/sparse-lru-file-readtwice-$i
> > truncate $sparse_file -s 36650387592
> > dd if=$sparse_file of=/dev/null &
> > dd if=$sparse_file of=/dev/null &
> > done
>
> So a page cache load of reading 120x36GB files twice concurrently?
Yes.
> There's no increase in system time, so it can't be that the
> shrinkers are running wild.
>
> FWIW, I'm at LCA right now, so it's going to be a week before I can
> look at this, so if you can find any behavioural difference in the
> shrinkers (e.g. from perf profiles, on different filesystems, etc)
> I'd appreciate it...
OK, enjoy your time! I'll try different parameters and check if that
makes any difference.
Thanks,
Fengguang
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Glauber Costa <glommer@parallels.com>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
lkp@linux.intel.com
Subject: Re: [numa shrinker] 9b17c62382: -36.6% regression on sparse file copy
Date: Wed, 8 Jan 2014 19:14:40 +0800 [thread overview]
Message-ID: <20140108111440.GA10467@localhost> (raw)
In-Reply-To: <20140106131042.GA5145@destitution>
On Tue, Jan 07, 2014 at 12:10:42AM +1100, Dave Chinner wrote:
> On Mon, Jan 06, 2014 at 04:20:48PM +0800, fengguang.wu@intel.com wrote:
> > Hi Dave,
> >
> > We noticed throughput drop in test case
> >
> > vm-scalability/300s-lru-file-readtwice (*)
> >
> > between v3.11 and v3.12, and it's still low as of v3.13-rc6:
> >
> > v3.11 v3.12 v3.13-rc6
> > --------------- ------------------------- -------------------------
> > 14934707 ~ 0% -48.8% 7647311 ~ 0% -47.6% 7829487 ~ 0% vm-scalability.throughput
> > ^^ ^^^^^^
> > stddev% change%
>
> What does this vm-scalability.throughput number mean?
It's the total throughput reported by all the 240 dd:
8781176832 bytes (8.8 GB) copied, 299.97 s, 29.3 MB/s
2124931+0 records in
2124930+0 records out
8703713280 bytes (8.7 GB) copied, 299.97 s, 29.0 MB/s
2174078+0 records in
2174077+0 records out
...
> > (*) The test case basically does
> >
> > truncate -s 135080058880 /tmp/vm-scalability.img
> > mkfs.xfs -q /tmp/vm-scalability.img
> > mount -o loop /tmp/vm-scalability.img /tmp/vm-scalability
> >
> > nr_cpu=120
> > for i in $(seq 1 $nr_cpu)
> > do
> > sparse_file=/tmp/vm-scalability/sparse-lru-file-readtwice-$i
> > truncate $sparse_file -s 36650387592
> > dd if=$sparse_file of=/dev/null &
> > dd if=$sparse_file of=/dev/null &
> > done
>
> So a page cache load of reading 120x36GB files twice concurrently?
Yes.
> There's no increase in system time, so it can't be that the
> shrinkers are running wild.
>
> FWIW, I'm at LCA right now, so it's going to be a week before I can
> look at this, so if you can find any behavioural difference in the
> shrinkers (e.g. from perf profiles, on different filesystems, etc)
> I'd appreciate it...
OK, enjoy your time! I'll try different parameters and check if that
makes any difference.
Thanks,
Fengguang
next prev parent reply other threads:[~2014-01-08 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 8:20 [numa shrinker] 9b17c62382: -36.6% regression on sparse file copy fengguang.wu
2014-01-06 8:20 ` fengguang.wu
2014-01-06 13:10 ` Dave Chinner
2014-01-06 13:10 ` Dave Chinner
2014-01-08 11:14 ` Fengguang Wu [this message]
2014-01-08 11:14 ` Fengguang Wu
2014-01-09 2:57 ` Fengguang Wu
2014-01-15 0:18 ` Dave Chinner
2014-01-15 0:18 ` Dave Chinner
2014-01-27 12:09 ` Fengguang Wu
2014-01-27 12:09 ` Fengguang Wu
2014-01-28 19:03 ` Tim Chen
2014-01-28 19:03 ` Tim Chen
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=20140108111440.GA10467@localhost \
--to=fengguang.wu@intel.com \
--cc=david@fromorbit.com \
--cc=glommer@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@linux.intel.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 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.