From nobody Thu May 9 01:58:56 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VZZv32yyWz5KDf6 for ; Thu, 09 May 2024 01:59:11 +0000 (UTC) (envelope-from mike.jakubik@gmail.com) Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VZZv14pSTz4vwQ for ; Thu, 9 May 2024 01:59:09 +0000 (UTC) (envelope-from mike.jakubik@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=WW5ghmPE; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mike.jakubik@gmail.com designates 2607:f8b0:4864:20::b2e as permitted sender) smtp.mailfrom=mike.jakubik@gmail.com Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-de60d05adafso410134276.2 for ; Wed, 08 May 2024 18:59:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715219948; x=1715824748; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=+oqX0PQyjWUfEBwsGxLcUVL7O6RwdrAG5Fhly3fde5U=; b=WW5ghmPEtgoaTTqVGHlSPyuYKLcZhXgk45nR42m+rdbQufH2Qhwy0ncmrcvXRTRHDJ AZJSjHp1kXLZRYAdORftBi3ONdETZl67P/tXAFsfwhHZas6og4TR4ABsb6dAmAsj9Kdb gNiXNyVbEAI/kpriv+lW2kLboqiwmy6k6zmH3ecH/GgRFCbZvrao1QzdEQu+wqVNkmFx IB7yVqAFHrZbgIfam7LOFMrRIL8qg6F0q/DCj2fs1ty8Oh3gh/zoKEPcbuJKFs/uhY+9 KiFcPW3SWLjOcOMjKcqdcwSxQ5JTUJ9JVo40Xybi68NDO8CM7SQz8iO+iXmHGdPuxwR3 3Z5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715219948; x=1715824748; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+oqX0PQyjWUfEBwsGxLcUVL7O6RwdrAG5Fhly3fde5U=; b=nk80frhElxCiEa7gwtbYHTS9rZIH5GW05s+nUrjBQBHJZw3rXEYucnyuEbwM2WpAiG cz/DnENYmCy/9J1GV69YksvpvyL70DDBAbfr51LRl06pXe4Mm2syMf44j8r1Ura1rRfl H7oobEgxOLAIrAZ4zbbMQzknQ5VlV/y5GLAE+G5OR2qJbf0rF8fQgP9QDV55RLOlEQ6f KDMRtzKqvgljqzsWgKlewyVPmLsUq980myHe0+ljCFOnUoZB+Sbw5BN/M3YKn1A61g9C rwDnxb4IQ0d4ba/t+deI9bejLz7qJb1fD/KBgxsMUn3DU3kQjQ0I62zpG8NqoG7hFUKF sugg== X-Forwarded-Encrypted: i=1; AJvYcCU9dBn7TTIYpWTk/3JqHvzFEyyl1IqvwkmQAlZdsvpoO/YB3fh8tTOes939Wxc279DZghktHnxRVO7ty9Xh53eUlrgd X-Gm-Message-State: AOJu0YwWAKgyb0RLjk0dZw4CjNur68wt2CtE8sBcZMXR/pJAhulZOboU BbMcFXKZszahuKFmDCdasQdlHQJAnSWgNwawZyff3bLXHUVc298hfgYfmMikc3owDrxDkZgRsNi qopWRau2fEr2egU6vyu1DqHgD74FqNJdZ9pw= X-Google-Smtp-Source: AGHT+IEY8zy/NnceVRBGqiSOILQvJnDJ4iTOEdj4R8exNp+mhQpoJbQxuB6ATAlhyu106Wy0W/zPxM0SiD0w5nvxO64= X-Received: by 2002:a05:6902:4f4:b0:de6:b58:fe72 with SMTP id 3f1490d57ef6-debb9dc3424mr4744913276.58.1715219948542; Wed, 08 May 2024 18:59:08 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <0a3ddc685e54a289ff5cff569a95cd29@Leidinger.net> In-Reply-To: <0a3ddc685e54a289ff5cff569a95cd29@Leidinger.net> From: Mike Jakubik Date: Wed, 8 May 2024 21:58:56 -0400 Message-ID: Subject: Re: Graph of the FreeBSD memory fragmentation To: Alexander Leidinger , current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000bea43b0617fbc33e" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.977]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TAGGED_FROM(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b2e:from] X-Rspamd-Queue-Id: 4VZZv14pSTz4vwQ --000000000000bea43b0617fbc33e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFAM Alexander Leidinger wrote: > Hi, > > I created some graphs of the memory fragmentation. > > > https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fra= gmentation/ > > 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=3D7a79d066976149349ecb90240d02eed= 0c4268737 > 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/PhysicalMemoryAntiFragm= entationMechanisms > ). > > Bye, > Alexander. > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF > --000000000000bea43b0617fbc33e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Alex,

No, i can't=C2=A0comment o= n the C code or it's change impact otherwise. But the graphs are impres= sive, i say lets try it. I can test i 14-stable.

T= y.

On Tue, May 7, 2024 at 8:03=E2=80=AFAM Alexander Leidinger <Alexander@leidinger.net> wrot= e:
Hi,

I created some graphs of the memory fragmentation.

https://www.leid= inger.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 o= f that,
Bojans commit
https://cgit.freeb= sd.org/src/commit/?id=3D7a79d066976149349ecb90240d02eed0c4268737
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/D4057= 5 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/PhysicalMemoryAntiFragmentationMe= chanisms).

Bye,
Alexander.

--
h= ttp://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF=
htt= p://www.FreeBSD.org=C2=A0 =C2=A0 netchild@FreeBSD.org=C2=A0 : PGP 0x8F3= 1830F9F2772BF
--000000000000bea43b0617fbc33e--