Graph of the FreeBSD memory fragmentation

[Alexander Leidinger]

Hi,

I created some graphs of the memory fragmentation.

https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fragmentation/

My goal was not comparing a specific change on a given benchmark, but to
"have something which visualizes memory fragmentation". As part of that,
Bojans commit
https://cgit.freebsd.org/src/commit/?id=7a79d066976149349ecb90240d02eed0c4268737
was just in the middle of my data collection. I have the impression that
it made a positive difference in my non deterministic workload.

Is there anything which prevents https://reviews.freebsd.org/D40575 to
be committed?

Maybe some other people want to have a look at the memory fragmentation
and some of Bojans work
(https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMechanisms).

Bye,
Alexander.

[Bojan Novković]

Hi,

Post by Alexander Leidinger
Hi,
I created some graphs of the memory fragmentation.
https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fragmentation/
My goal was not comparing a specific change on a given benchmark, but
to "have something which visualizes memory fragmentation". As part of
that, Bojans commit
https://cgit.freebsd.org/src/commit/?id=7a79d066976149349ecb90240d02eed0c4268737
was just in the middle of my data collection. I have the impression
that it made a positive difference in my non deterministic workload.

Thank you for working on this, the plots look great!
They provide a really clean visual overview of what's happening.
I'm working on another type of memory visualization which might interest
you, I'll share it with you once its done.
One small nit - the fragmentation index does not quantify fragmentation
for UMA buckets, but for page allocator freelists.

Post by Alexander Leidinger
Is there anything which prevents https://reviews.freebsd.org/D40575 to
be committed?

D40575 is closely tied to the compaction patch (D40772) which is
currently on hold until another issue is solved (see D45046 and related
revisions for more details).
I didn't consider landing D40575 because of that, but I guess it could
be useful on its own.


Bojan



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Mike Jakubik]

Hi Alex,

No, i can't comment on the C code or it's change impact otherwise. But the
graphs are impressive, i say lets try it. I can test i 14-stable.

Ty.

Post by Alexander Leidinger
Hi,
I created some graphs of the memory fragmentation.
https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fragmentation/
My goal was not comparing a specific change on a given benchmark, but to
"have something which visualizes memory fragmentation". As part of that,
Bojans commit
https://cgit.freebsd.org/src/commit/?id=7a79d066976149349ecb90240d02eed0c4268737
was just in the middle of my data collection. I have the impression that
it made a positive difference in my non deterministic workload.
Is there anything which prevents https://reviews.freebsd.org/D40575 to
be committed?
Maybe some other people want to have a look at the memory fragmentation
and some of Bojans work
(
https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMechanisms
).
Bye,
Alexander.
--