From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Randy MacLeod <randy.macleod@windriver.com>,
raj.khem@gmail.com, "Kokkonda,
Sundeep" <Sundeep.Kokkonda@windriver.com>,
"Shinde, Yash" <yash.shinde@windriver.com>,
Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] rust-llvm: Compile llvm to use dynamic libraries
Date: Tue, 01 Apr 2025 08:34:58 +0100 [thread overview]
Message-ID: <0ffd9405cc6d36130436edcbffef826dc3f29b4b.camel@linuxfoundation.org> (raw)
In-Reply-To: <1832019BE8984F8C.2063@lists.openembedded.org>
On Mon, 2025-03-31 at 22:49 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Mon, 2025-03-31 at 21:44 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Mon, 2025-03-31 at 15:08 -0400, Randy MacLeod wrote:
> > >
> > > On 2025-03-31 12:13 p.m., Khem Raj via lists.openembedded.org
> > > wrote:
> > >
> > > > On Mon, Mar 31, 2025 at 6:30 AM Richard Purdie via
> > > > lists.openembedded.org
> > > > <richard.purdie=linuxfoundation.org@lists.openembedded.org>
> > > > wrote:
> > > > > Our main llvm recipe uses dynamic linking already but rust-
> > > > > llvm
> > > > > does not.
> > > > > Enabling this significanly reduces the size of llvm-rust to
> > > > > about a third
> > > > > of what it was, which is a bettter configuration for us
> > > > > leading to smaller
> > > > > TMPDIR and sstate objects
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > It will slow down the compiler execution and sometimes its
> > > > could
> > > > be significant as well we have seen this with clang so it would
> > > > be good to have some idea around that least we provide a slow
> > > > compiler compared to other distro infrastructures
> > > >
> > > >
> > > >
> > > >
> > >
> > > We'll get some performance info from the YP AB perf builds.
> >
> > https://valkyrie.yocto.io/pub/non-release/20250331-105/testresults/buildperf-debian11/perf-debian12-vk_master-next_20250331181527_9ba5b4f4e4.html
> > https://valkyrie.yocto.io/pub/non-release/20250331-104/testresults/buildperf-alma8/perf-alma8-vk_master-next_20250331181513_9ba5b4f4e4.html
> >
> > The build time is fractionally faster (1%?) but hard to say within
> > noise.
> >
> > The diskspace drop is convincing, 2.3GB less TMPDIR size (2.3%).
> >
> > The rm_work TMPDIR size also drops by 1GB (6%) which is
> > particularly
> > significant and nice to have.
> >
> > In builds with rust-llvm as well as rust-llvm-native, this will
> > double up for a double win.
>
> The analysis is a bit flawed as it is contrasting master with master-
> next which has 1.85 as well as other changes. We need to remove that
> from the equation.
There are a direct comparison with just the patch added:
https://valkyrie.yocto.io/pub/non-release/20250331-129/testresults/buildperf-debian11/perf-debian12-vk_master-next_20250331220727_26fa862acd.html
https://valkyrie.yocto.io/pub/non-release/20250331-128/testresults/buildperf-alma8/perf-alma8-vk_master-next_20250331220715_26fa862acd.html
So the buildtime is around the same (or less with rm_work), it is hard
to say from the daya. TMPDIR is 3.6GB less and 1GB less with rm_work so
definitely improved.
Enough of an improvement in space usage I think this is worthwhile. In
general space usage does correlate with build speed.
Cheers,
Richard
next prev parent reply other threads:[~2025-04-01 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 13:30 [PATCH] rust-llvm: Compile llvm to use dynamic libraries Richard Purdie
2025-03-31 16:13 ` [OE-core] " Khem Raj
2025-03-31 19:08 ` Randy MacLeod
2025-03-31 20:44 ` Richard Purdie
2025-03-31 21:49 ` Khem Raj
[not found] ` <1831FE10390FE3BE.19875@lists.openembedded.org>
2025-03-31 21:49 ` Richard Purdie
[not found] ` <1832019BE8984F8C.2063@lists.openembedded.org>
2025-04-01 7:34 ` Richard Purdie [this message]
2025-04-01 14:19 ` Khem Raj
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=0ffd9405cc6d36130436edcbffef826dc3f29b4b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Deepesh.Varatharajan@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.com \
--cc=yash.shinde@windriver.com \
/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