News: 0001576947

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Linux's New "Sheaves" Per-CPU Caching Layer Showing Massive Wins For AMD Performance

([AMD] 5 Hours Ago Sheaves Benchmarks)


Earlier this week I wrote about [1]Sheaves as an opt-in, per-CPU array-based caching layer likely coming for Linux 6.18. The sheaves patches have been queued into the "slab/for-next" Git branch ahead of the Linux 6.18 kernel merge window. Patches posted now by Google are showing the Linux Sheaves code having a massive beneficial impact for large AMD systems.

Google engineer Sudarsan Mahendran posted some benchmarks of the SLUB per-CPU Sheaves patches on Friday. The patches were applied to a Linux 6.17 base and tested across AMD, Intel, and ARM servers. For the AMD EPYC Turin server the Sheaves work ended up being a massive win for performance on a number of benchmarks but also some regressions.

Sudarsan Mahendran [2]commented on the mailing list:

"I ported this patch series on top of v6.17 and ran some benchmarks: will-it-scale, hackbench, redis, unixbench and kernbench. I ran the benchmarks on Intel Granite Rapids (480 cores), AMD Turin (512 cores) and ARM (80 cores)

Summary of the results:

- Significant change (meaning >10% difference between base and experiment) on will-it-scale tests in AMD.

- No significant change on other benchmarks ran."

Going over his benchmarks on that LKML thread were exciting when seeing "+28.58%" mean improvements to get started, but also some 13~20% regressions... But when getting to the higher process counts for these scalability benchmarks was when it was getting really wild with +70.59%, +126.89%, +112.89%, and other massive wins. See all of the Google engineer's data in [3]this thread .

It will be exciting to see how the Sheaves patches play out in more real-world workloads. Once these patches hit the mainline kernel presumably for Linux 6.18, I'll be firing up a number of benchmarks on my own hardware and thankfully have a lot of AMD EPYC Turin hardware and more for some exciting benchmarks ahead.



[1] https://www.phoronix.com/news/Linux-6.18-Likely-Sheaves

[2] https://lore.kernel.org/lkml/20250913000935.1021068-1-sudarsanm@google.com/

[3] https://lore.kernel.org/lkml/20250913000935.1021068-1-sudarsanm@google.com/



Kjell

V1tol

ezst036

If you throw a New Year's Party, the worst thing that you can do would be
to throw the kind of party where your guests wake up today, and call you to
say they had a nice time. Now you'll be be expected to throw another party
next year.
What you should do is throw the kind of party where your guest wake
up several days from now and call their lawyers to find out if they've been
indicted for anything. You want your guests to be so anxious to avoid a
recurrence of your party that they immediately start planning parties of their
own, a year in advance, just to prevent you from having another one ...
If your party is successful, the police will knock on your door,
unless your party is very successful in which case they will lob tear gas
through your living room window. As host, your job is to make sure that
they don't arrest anybody. Or if they're dead set on arresting someone,
your job is to make sure it isn't you ...
-- Dave Barry