Date: Wed, 8 May 2024 21:58:56 -0400 From: Mike Jakubik <mike.jakubik@gmail.com> To: Alexander Leidinger <Alexander@leidinger.net>, current@freebsd.org Subject: Re: Graph of the FreeBSD memory fragmentation Message-ID: <CABk=mnhQ-hF3Fh%2B9FTJ62SThBF3J5qW7r6Fhf9jnjqajpCBE1g@mail.gmail.com> In-Reply-To: <0a3ddc685e54a289ff5cff569a95cd29@Leidinger.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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. On Tue, May 7, 2024 at 8:03 AM Alexander Leidinger <Alexander@leidinger.net> wrote: > 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. > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF > [-- Attachment #2 --] <div dir="ltr">Hi Alex,<div><br></div><div>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.</div><div><br></div><div>Ty.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 7, 2024 at 8:03 AM Alexander Leidinger <<a href="mailto:Alexander@leidinger.net">Alexander@leidinger.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br> <br> I created some graphs of the memory fragmentation.<br> <br> <a href="https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fragmentation/" rel="noreferrer" target="_blank">https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fragmentation/</a><br>; <br> My goal was not comparing a specific change on a given benchmark, but to <br> "have something which visualizes memory fragmentation". As part of that, <br> Bojans commit <br> <a href="https://cgit.freebsd.org/src/commit/?id=7a79d066976149349ecb90240d02eed0c4268737" rel="noreferrer" target="_blank">https://cgit.freebsd.org/src/commit/?id=7a79d066976149349ecb90240d02eed0c4268737</a>; <br> was just in the middle of my data collection. I have the impression that <br> it made a positive difference in my non deterministic workload.<br> <br> Is there anything which prevents <a href="https://reviews.freebsd.org/D40575" rel="noreferrer" target="_blank">https://reviews.freebsd.org/D40575</a>; to <br> be committed?<br> <br> Maybe some other people want to have a look at the memory fragmentation <br> and some of Bojans work <br> (<a href="https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMechanisms" rel="noreferrer" target="_blank">https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMechanisms</a>).<br>; <br> Bye,<br> Alexander.<br> <br> -- <br> <a href="http://www.Leidinger.net" rel="noreferrer" target="_blank">http://www.Leidinger.net</a>; Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF<br> <a href="http://www.FreeBSD.org" rel="noreferrer" target="_blank">http://www.FreeBSD.org</a>  netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF<br> </blockquote></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABk=mnhQ-hF3Fh%2B9FTJ62SThBF3J5qW7r6Fhf9jnjqajpCBE1g>