From: Uladzislau Rezki <urezki@gmail.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
Vlastimil Babka <vbabka@suse.cz>,
paulmck@kernel.org, Jan Engelhardt <ej@inai.de>,
Sudarsan Mahendran <sudarsanm@google.com>,
Liam.Howlett@oracle.com, cl@gentwo.org, harry.yoo@oracle.com,
howlett@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, maple-tree@lists.infradead.org,
rcu@vger.kernel.org, rientjes@google.com,
roman.gushchin@linux.dev
Subject: Re: Benchmarking [PATCH v5 00/14] SLUB percpu sheaves
Date: Thu, 18 Sep 2025 13:50:12 +0200 [thread overview]
Message-ID: <aMvx9GKgIWtrkZ_R@milan> (raw)
In-Reply-To: <CAJuCfpE48n=QM0nY8yE3drqZU0wgC76=70EyftL1WZewEcykyA@mail.gmail.com>
On Wed, Sep 17, 2025 at 04:59:41PM -0700, Suren Baghdasaryan wrote:
> On Wed, Sep 17, 2025 at 9:14 AM Suren Baghdasaryan <surenb@google.com> wrote:
> >
> > On Tue, Sep 16, 2025 at 10:19 PM Uladzislau Rezki <urezki@gmail.com> wrote:
> > >
> > > On Tue, Sep 16, 2025 at 10:09:18AM -0700, Suren Baghdasaryan wrote:
> > > > On Mon, Sep 15, 2025 at 8:22 AM Vlastimil Babka <vbabka@suse.cz> wrote:
> > > > >
> > > > > On 9/15/25 14:13, Paul E. McKenney wrote:
> > > > > > On Mon, Sep 15, 2025 at 09:51:25AM +0200, Jan Engelhardt wrote:
> > > > > >>
> > > > > >> On Saturday 2025-09-13 02:09, Sudarsan Mahendran wrote:
> > > > > >> >
> > > > > >> >Summary of the results:
> > > > >
> > > > > In any case, thanks a lot for the results!
> > > > >
> > > > > >> >- Significant change (meaning >10% difference
> > > > > >> > between base and experiment) on will-it-scale
> > > > > >> > tests in AMD.
> > > > > >> >
> > > > > >> >Summary of AMD will-it-scale test changes:
> > > > > >> >
> > > > > >> >Number of runs : 15
> > > > > >> >Direction : + is good
> > > > > >>
> > > > > >> If STDDEV grows more than mean, there is more jitter,
> > > > > >> which is not "good".
> > > > > >
> > > > > > This is true. On the other hand, the mean grew way more in absolute
> > > > > > terms than did STDDEV. So might this be a reasonable tradeoff?
> > > > >
> > > > > Also I'd point out that MIN of TEST is better than MAX of BASE, which means
> > > > > there's always an improvement for this config. So jitter here means it's
> > > > > changing between better and more better :) and not between worse and (more)
> > > > > better.
> > > > >
> > > > > The annoying part of course is that for other configs it's consistently the
> > > > > opposite.
> > > >
> > > > Hi Vlastimil,
> > > > I ran my mmap stress test that runs 20000 cycles of mmapping 50 VMAs,
> > > > faulting them in then unmapping and timing only mmap and munmap calls.
> > > > This is not a realistic scenario but works well for A/B comparison.
> > > >
> > > > The numbers are below with sheaves showing a clear improvement:
> > > >
> > > > Baseline
> > > > avg stdev
> > > > mmap 2.621073 0.2525161631
> > > > munmap 2.292965 0.008831973052
> > > > total 4.914038 0.2572620923
> > > >
> > > > Sheaves
> > > > avg stdev avg_diff stdev_diff
> > > > mmap 1.561220667 0.07748897037 -40.44% -69.31%
> > > > munmap 2.042071 0.03603083448 -10.94% 307.96%
> > > > total 3.603291667 0.113209047 -26.67% -55.99%
> > > >
> > > Could you run your test with dropping below patch?
> >
> > Sure, will try later today and report.
>
> Sheaves with [04/23] patch reverted:
>
> avg avg_diff
> mmap 2.143948 -18.20%
> munmap 2.343707 2.21%
> total 4.487655 -8.68%
>
With offloading over sheaves the mmap/munmap is faster, i assume it is
because of same objects are reused from the sheaves after reclaim. Whereas we,
kvfree_rcu() just free them.
Thank you for your results.
--
Uladzislau Rezki
next prev parent reply other threads:[~2025-09-18 11:50 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 13:34 [PATCH v5 00/14] SLUB percpu sheaves Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 01/14] slab: add opt-in caching layer of " Vlastimil Babka
2025-08-18 10:09 ` Harry Yoo
2025-08-26 8:03 ` Vlastimil Babka
2025-08-19 4:19 ` Suren Baghdasaryan
2025-08-26 8:51 ` Vlastimil Babka
2025-09-13 14:35 ` Mateusz Guzik
2025-09-13 20:32 ` Vlastimil Babka
2025-09-14 2:22 ` Hillf Danton
2025-09-14 20:24 ` Vlastimil Babka
2025-09-15 0:11 ` Hillf Danton
2025-09-15 7:21 ` Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 02/14] slab: add sheaf support for batching kfree_rcu() operations Vlastimil Babka
2025-07-23 16:39 ` Uladzislau Rezki
2025-07-24 14:30 ` Vlastimil Babka
2025-07-24 17:36 ` Uladzislau Rezki
2025-07-23 13:34 ` [PATCH v5 03/14] slab: sheaf prefilling for guaranteed allocations Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 04/14] slab: determine barn status racily outside of lock Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 05/14] tools: Add testing support for changes to rcu and slab for sheaves Vlastimil Babka
2025-08-22 16:28 ` Suren Baghdasaryan
2025-08-26 9:32 ` Vlastimil Babka
2025-08-27 0:19 ` Suren Baghdasaryan
2025-07-23 13:34 ` [PATCH v5 06/14] tools: Add sheaves support to testing infrastructure Vlastimil Babka
2025-08-22 16:56 ` Suren Baghdasaryan
2025-08-26 9:59 ` Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 07/14] maple_tree: use percpu sheaves for maple_node_cache Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 08/14] mm, vma: use percpu sheaves for vm_area_struct cache Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 09/14] mm, slub: skip percpu sheaves for remote object freeing Vlastimil Babka
2025-08-25 5:22 ` Harry Yoo
2025-08-26 10:11 ` Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 10/14] mm, slab: allow NUMA restricted allocations to use percpu sheaves Vlastimil Babka
2025-08-22 19:58 ` Suren Baghdasaryan
2025-08-25 6:52 ` Harry Yoo
2025-08-26 10:49 ` Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 11/14] testing/radix-tree/maple: Increase readers and reduce delay for faster machines Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 12/14] maple_tree: Sheaf conversion Vlastimil Babka
2025-08-22 20:18 ` Suren Baghdasaryan
2025-08-26 14:22 ` Liam R. Howlett
2025-08-27 2:07 ` Suren Baghdasaryan
2025-08-28 14:27 ` Liam R. Howlett
2025-07-23 13:34 ` [PATCH v5 13/14] maple_tree: Add single node allocation support to maple state Vlastimil Babka
2025-08-22 20:25 ` Suren Baghdasaryan
2025-08-26 15:10 ` Liam R. Howlett
2025-08-27 2:03 ` Suren Baghdasaryan
2025-07-23 13:34 ` [PATCH v5 14/14] maple_tree: Convert forking to use the sheaf interface Vlastimil Babka
2025-08-22 20:29 ` Suren Baghdasaryan
2025-08-15 22:53 ` [PATCH v5 00/14] SLUB percpu sheaves Sudarsan Mahendran
2025-08-16 8:05 ` Harry Yoo
2025-08-16 17:35 ` Sudarsan Mahendran
2025-08-16 18:31 ` Vlastimil Babka
2025-08-16 18:33 ` Vlastimil Babka
2025-08-17 4:28 ` Sudarsan Mahendran
2025-09-13 0:09 ` Benchmarking " Sudarsan Mahendran
2025-09-15 7:51 ` Jan Engelhardt
2025-09-15 12:13 ` Paul E. McKenney
2025-09-15 15:22 ` Vlastimil Babka
2025-09-16 17:09 ` Suren Baghdasaryan
2025-09-17 5:19 ` Uladzislau Rezki
2025-09-17 16:14 ` Suren Baghdasaryan
2025-09-17 23:59 ` Suren Baghdasaryan
2025-09-18 11:50 ` Uladzislau Rezki [this message]
2025-09-18 15:29 ` Liam R. Howlett
2025-09-19 15:07 ` Uladzislau Rezki
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=aMvx9GKgIWtrkZ_R@milan \
--to=urezki@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=cl@gentwo.org \
--cc=ej@inai.de \
--cc=harry.yoo@oracle.com \
--cc=howlett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=sudarsanm@google.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).