public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] cargo.eclass: Optimize crate unpacking
Date: Sun, 12 May 2024 20:21:27 +0200	[thread overview]
Message-ID: <849a540bd028ac0fed47c75c71ecf077f703c28d.camel@gentoo.org> (raw)
In-Reply-To: <6c25db91-4a22-48d5-b639-8009487fb7bf@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2715 bytes --]

On Sun, 2024-05-12 at 19:22 +0200, Florian Schmaus wrote:
> On 12/05/2024 04.26, Michał Górny wrote:
> > Unpack crates in parallel using xargs to utilize multicore systems
> > better.  Perform checksumming via a single sha256sum invocation.
> > 
> > For dev-python/watchfiles, this speeds up unpacking on my machine
> > from 2.6 s to 0.75 s (warm cache).
> > 
> > Signed-off-by: Michał Górny <mgorny@gentoo.org>
> > ---
> >   eclass/cargo.eclass | 56 ++++++++++++++++++++++++++-------------------
> >   1 file changed, 33 insertions(+), 23 deletions(-)
> > 
> > diff --git a/eclass/cargo.eclass b/eclass/cargo.eclass
> > index 0f2da982f60c..5a16d3a30528 100644
> > --- a/eclass/cargo.eclass
> > +++ b/eclass/cargo.eclass
> > @@ -329,40 +329,50 @@ _cargo_gen_git_config() {
> >   cargo_src_unpack() {
> >   	debug-print-function ${FUNCNAME} "$@"
> >   
> > -	mkdir -p "${ECARGO_VENDOR}" || die
> > -	mkdir -p "${S}" || die
> > +	mkdir -p "${ECARGO_VENDOR}" "${S}" || die
> >   
> >   	local archive shasum pkg
> > +	local crates=()
> >   	for archive in ${A}; do
> >   		case "${archive}" in
> >   			*.crate)
> > -				# when called by pkgdiff-mg, do not unpack crates
> > -				[[ ${PKGBUMPING} == ${PVR} ]] && continue
> > -
> > -				ebegin "Loading ${archive} into Cargo registry"
> > -				tar -xf "${DISTDIR}"/${archive} -C "${ECARGO_VENDOR}/" || die
> > -				# generate sha256sum of the crate itself as cargo needs this
> > -				shasum=$(sha256sum "${DISTDIR}"/${archive} | cut -d ' ' -f 1)
> > -				pkg=$(basename ${archive} .crate)
> > -				cat <<- EOF > ${ECARGO_VENDOR}/${pkg}/.cargo-checksum.json
> > -				{
> > -					"package": "${shasum}",
> > -					"files": {}
> > -				}
> > -				EOF
> > -				# if this is our target package we need it in ${WORKDIR} too
> > -				# to make ${S} (and handle any revisions too)
> > -				if [[ ${P} == ${pkg}* ]]; then
> > -					tar -xf "${DISTDIR}"/${archive} -C "${WORKDIR}" || die
> > -				fi
> > -				eend $?
> > +				crates+=( "${archive}" )
> >   				;;
> >   			*)
> > -				unpack ${archive}
> > +				unpack "${archive}"
> >   				;;
> >   		esac
> >   	done
> >   
> > +	if [[ ${PKGBUMPING} != ${PVR} ]]; then
> > +		pushd "${DISTDIR}" >/dev/null || die
> > +
> > +		ebegin "Unpacking crates"
> > +		printf '%s\0' "${crates[@]}" |
> > +			xargs -0 -P "$(makeopts_jobs)" -n 1 -- \
> 
> Consider using get_makeopts_jobs instead of makeopts_jobs, as it 
> searches more variables for --jobs.

Whose bright idea was to add a second similarly named function that does
roughly the same thing but apparently differently?  It can hardly get
more confusing.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

  reply	other threads:[~2024-05-12 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12  2:26 [gentoo-dev] [PATCH] cargo.eclass: Optimize crate unpacking Michał Górny
2024-05-12  2:44 ` Sam James
2024-05-12 17:22 ` Florian Schmaus
2024-05-12 18:21   ` Michał Górny [this message]
2024-05-13 14:00     ` Florian Schmaus
2024-05-13 14:02       ` Michał Górny
2024-05-16  6:55     ` [gentoo-dev] Obtaining values for --jobs and --load-average Florian Schmaus

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=849a540bd028ac0fed47c75c71ecf077f703c28d.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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