From: Suren Baghdasaryan <surenb@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@techsingularity.net>
Cc: linux-mm <linux-mm@kvack.org>
Subject: ptf-threads on mm-unstable seems to regressed from 6.2-rc3
Date: Sat, 21 Jan 2023 23:28:17 -0800 [thread overview]
Message-ID: <CAJuCfpGr5RBaKdG-abnKMqMDDCAECgseaZBW-gKbyFhSbMtC9Q@mail.gmail.com> (raw)
Hi Andrew and Mel,
While testing per-vma locks on mm-unstable branch I noticed a sizable
regression when running pft-threads test from Mel's mmtests suite:
BASE MM_UNSTABLE
Hmean faults/sec-1 469201.7282 ( 0.00%) 305002.3892 * -35.00%*
Hmean faults/sec-4 1754465.6221 ( 0.00%) 1183736.3124 * -32.53%*
Hmean faults/sec-7 2808141.6711 ( 0.00%) 1964469.4590 * -30.04%*
Hmean faults/sec-12 3750307.7553 ( 0.00%) 2811359.5393 * -25.04%*
Hmean faults/sec-21 4145672.4677 ( 0.00%) 3082305.9582 * -25.65%*
Hmean faults/sec-30 3775722.5726 ( 0.00%) 2918088.2083 * -22.71%*
Hmean faults/sec-48 4152563.5864 ( 0.00%) 3219418.0414 * -22.47%*
Hmean faults/sec-56 4163868.7111 ( 0.00%) 3124612.3198 * -24.96%*
This is comparing mm-unstable ToT (c04e06325f11 "mm: multi-gen LRU:
simplify lru_gen_look_around()") with 6.2-rc3, which was my previous
baseline (both are tested without my patchset). Not sure if this is
expected, so sending a warning. If this is unexpected, it would also
be great if someone can confirm this is not a fluke on my side.
The test machine I use is a NUMA 2-socket Intel Xeon E5-2690-v4
(Broadwell microarchitecture).
Command I used to reproduce is:
run-mmtests.sh --no-monitor --config configs/config-workload-pft-threads <name>
Thanks,
Suren.
next reply other threads:[~2023-01-22 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 7:28 Suren Baghdasaryan [this message]
2023-01-22 18:53 ` T.J. Alumbaugh
2023-01-22 23:09 ` Suren Baghdasaryan
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=CAJuCfpGr5RBaKdG-abnKMqMDDCAECgseaZBW-gKbyFhSbMtC9Q@mail.gmail.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
/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