From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Brian Inglis <Brian.Inglis@Shaw.ca>
Subject: Re: cygport 0.36.2-1
Date: Fri, 14 Apr 2023 16:51:16 +0100 [thread overview]
Message-ID: <993e7488-b5a2-cc8f-c898-fd5c3ceda934@dronecode.org.uk> (raw)
In-Reply-To: <5502290c-8747-ca07-8d1e-94bac8f7cbea@Shaw.ca>
On 13/04/2023 17:51, Brian Inglis via Cygwin-apps wrote:
> On 2023-04-13 10:27, Jon Turney via Cygwin-apps wrote:
>> On 13/04/2023 17:20, Jon Turney via Cygwin-apps wrote:
>>> The following packages have been uploaded to the Cygwin distribution:
>>> * cygport-0.36.1-1
>
>> Oops. Wrong list. Sorry.
>
> No worries ;^>
>
> While you're here, I just recently noticed that xargs has a flag:
>
> -P, --max-procs[ =]max-procs
>
> so we can easily use `nproc`, $((`nproc`+1)) like make, or
> $((`nproc`-1)) to be nice, to handle parallelizable commands on long
> lists of files, perhaps for Preparing debuginfo source files?
Perhaps. I suspect that step maybe largely I/O bound, since I think it
mainly copies a lot of files. (maybe it doesn't need to, and hard links
would work just as well, idk)
Ideally, the first step in making some performance improvements would be
to actually profile the existing code in some way, to generate some
evidence which identifies places where effort would be best spent,
rather than randomly parallelizing whatever strikes your fancy... but
then again, I'm not working on it, so you can do whatever you like...
prev parent reply other threads:[~2023-04-14 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 16:20 Jon Turney
2023-04-13 16:27 ` Jon Turney
2023-04-13 16:51 ` Brian Inglis
2023-04-14 15:51 ` Jon Turney [this message]
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=993e7488-b5a2-cc8f-c898-fd5c3ceda934@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Brian.Inglis@Shaw.ca \
--cc=cygwin-apps@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).