From: Rik Kabel <rik@panix.com>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: new upload
Date: Tue, 18 Jul 2023 17:53:15 -0400 [thread overview]
Message-ID: <107a8941-9711-93ac-3c10-053287413652@panix.com> (raw)
In-Reply-To: <bb657f3a-c742-827e-99e3-c962966f7474@xs4all.nl>
On 7/18/2023 4:12 PM, Hans Hagen wrote:
> Hi,
>
> In todays upload there is a follow up on a new feature that is already
> present in the previous upload (but that was not yet advertised):
>
> context --parallel test1.tex test2.tex test3.tex
>
> context --parallel --pattern=test*.tex
>
> context --parallellist myfile.cmd (filters context processing lines)
>
> context --parallel test1.tex test2.tex test3.tex --terminal
>
> The --parellel feature will run in parallel, By default upto 8 jobs
> but you can specify less or more depending on your hardware but on my
> machine this is reasonable.
>
> See workflows-parrallel at the end for more info. That one also
> mentions the new --forceinput flag which makes that when these
>
> context foo-1.tex --mode=m-1 --forceinput=whatever.tex
> context foo-3.tex --mode=m-3 --forceinput=whatever.tex
>
> are run in parallel there is no clash in tuc/pdf. Of course not all
> scenarios might work out well. Commandline arguments given are passed
> on to the different jobs but it's good enough for the purpose I have
> in mind.
>
> fwiw: a single pass teststuite run (some 1950 files) goes down from
> 1350 to 700 seconds but another run with 1200 complex xml documents
> goes 4 times faster. In the end this is way cheaper than updating a 5
> year old dev machine (a new one would run about twice as fast which
> would bring about the same gain).
>
> Hans
>
> ps. Because tex is a memory intense application it doesn't scale with
> the number of cores unless one has the latest greatest fast memory as
> well as generous cpu caches. There's only so much one can do in the
> code base about it.
>
>
Nice. Some of my make files use concurrence (MAKEFLAGS += --jobs=5).
That seems to bring similar benefits. Is this different beyond the syntax?
--
Rik
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-07-18 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 20:12 [NTG-context] " Hans Hagen
2023-07-18 21:53 ` Rik Kabel [this message]
2023-07-19 6:37 ` [NTG-context] " Hans Hagen via ntg-context
2023-08-15 17:08 [NTG-context] " Hans Hagen
2023-08-15 19:27 ` [NTG-context] " Pablo Rodriguez
2023-08-15 20:16 ` Hans Hagen via ntg-context
2023-08-15 20:54 ` Pablo Rodriguez
2023-08-16 8:07 ` Hans Hagen via ntg-context
2023-08-16 17:46 ` Hans Hagen via ntg-context
2023-08-17 13:39 ` Pablo Rodriguez
2023-09-04 17:22 [NTG-context] " Hans Hagen
2023-09-04 17:37 ` [NTG-context] " Pablo Rodriguez
2024-06-18 20:15 [NTG-context] " Hans Hagen
2024-06-19 16:55 ` [NTG-context] " Pablo Rodriguez via ntg-context
2025-02-04 16:59 [NTG-context] " Hans Hagen
2025-02-04 18:12 ` [NTG-context] " Rik Kabel
2025-02-04 20:12 ` Wolfgang Schuster
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=107a8941-9711-93ac-3c10-053287413652@panix.com \
--to=rik@panix.com \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).