All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonsoo Kim <js1304@gmail.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Vlastimil Babka <vbabka@suse.cz>, Hugh Dickins <hughd@google.com>,
	Matthew Wilcox <willy@infradead.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	Michal Hocko <mhocko@kernel.org>,
	Minchan Kim <minchan@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org, lkp@intel.com, ying.huang@intel.com,
	feng.tang@intel.com, zhengjun.xing@intel.com
Subject: Re: [mm/swap]  aae466b005:  vm-scalability.throughput -2.7% regression
Date: Mon, 4 Jan 2021 10:24:10 +0900	[thread overview]
Message-ID: <20210104012356.GA5941@js1304-desktop> (raw)
In-Reply-To: <20201230062412.GD22185@xsang-OptiPlex-9020>

On Wed, Dec 30, 2020 at 02:24:12PM +0800, kernel test robot wrote:
> 
> Greeting,
> 
> FYI, we noticed a -2.7% regression of vm-scalability.throughput due to commit:
> 
> 
> commit: aae466b0052e1888edd1d7f473d4310d64936196 ("mm/swap: implement workingset detection for anonymous LRU")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

Hello,

Thanks for reporting.

This is a known issue to me. As you can see below, slight regression
is found on only the random access workload. For pure random pattern,
detecting workingset would not guarantee a good result since these
pages doesn't accessed in the near future. Even worse, it causes small
overhead to the system since we need to demote these activated page to
the inactive list to reclaim. So, below result is natural to me.

For other access pattern, this patchset would result in positive
effect.

Thanks.


WARNING: multiple messages have this Message-ID (diff)
From: Joonsoo Kim <js1304@gmail.com>
To: lkp@lists.01.org
Subject: Re: [mm/swap] aae466b005: vm-scalability.throughput -2.7% regression
Date: Mon, 04 Jan 2021 10:24:10 +0900	[thread overview]
Message-ID: <20210104012356.GA5941@js1304-desktop> (raw)
In-Reply-To: <20201230062412.GD22185@xsang-OptiPlex-9020>

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

On Wed, Dec 30, 2020 at 02:24:12PM +0800, kernel test robot wrote:
> 
> Greeting,
> 
> FYI, we noticed a -2.7% regression of vm-scalability.throughput due to commit:
> 
> 
> commit: aae466b0052e1888edd1d7f473d4310d64936196 ("mm/swap: implement workingset detection for anonymous LRU")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

Hello,

Thanks for reporting.

This is a known issue to me. As you can see below, slight regression
is found on only the random access workload. For pure random pattern,
detecting workingset would not guarantee a good result since these
pages doesn't accessed in the near future. Even worse, it causes small
overhead to the system since we need to demote these activated page to
the inactive list to reclaim. So, below result is natural to me.

For other access pattern, this patchset would result in positive
effect.

Thanks.

  reply	other threads:[~2021-01-04  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30  6:24 [mm/swap] aae466b005: vm-scalability.throughput -2.7% regression kernel test robot
2020-12-30  6:24 ` kernel test robot
2021-01-04  1:24 ` Joonsoo Kim [this message]
2021-01-04  1:24   ` Joonsoo Kim

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=20210104012356.GA5941@js1304-desktop \
    --to=js1304@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=feng.tang@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=minchan@kernel.org \
    --cc=oliver.sang@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.com \
    --cc=zhengjun.xing@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.