On 6/22/2025 6:03 PM, John Was wrote:
Yes, it's an odd thing - even odder now since the last two runs have been much faster.  This without any intervention from me.  It will be interesting to see what happens when I switch off and resume tomorrow. But it's not a serious issue for me at the moment since I'm only using the machine to experiment with various features of the program.

just try this after a fresh start:

context --make

context --make

and note the difference in reported time ... the operating system caches files and programs like tex benefits from this

in the past when running on a network share - in most cases we use(d) opensuse linux servers - using e.g. installations like texlive was basically impossible due to the size which is why we had the minimal distributions, also for pdfex/mkii; i think that over time kpse lookups improved a bit but is is one of the reasons why we had agressive caching in the runners (texexec etc) just so to limit the number of nested kpsewhich database loading overhead and kept startup time bearable

in the meantime startup time of a context run in lmtx should be below .5 seconds and that includes the runner as well as the engine (and on modern systems below .25 sec but i can't check that as i only have laptop hardware pre 2018 to test on)

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

Reply via email to