ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Why LuaMetaTex is so slow?
Date: Fri, 19 Jan 2024 19:30:18 +0100	[thread overview]
Message-ID: <d05e771a-4d9d-4a7a-97d9-e214e15a6744@xs4all.nl> (raw)
In-Reply-To: <D95DD995-BF8E-4CC3-B9A0-529F31526E2D@scorecrow.com>

On 1/19/2024 7:13 PM, Bruce Horrocks wrote:
> 
> 
>> On 19 Jan 2024, at 09:31, Hans Hagen <j.hagen@xs4all.nl> wrote:
>>
>> On 1/18/2024 11:15 PM, Bruce Horrocks wrote:
>>> On 18 Jan 2024, at 18:56, Shiv Shankar Dayal <shivshankar.dayal@gmail.com> wrote:
>>>>
>>>> I understand that why it is slow, but the problem is that the difference is too high.
>>>> My book has lots of math, so perhaps that is the reason.
>>> Option 1: Buy or borrow a faster computer. You'll get your desired speed-up far faster than waiting for Hans to make changes, even assuming there is something that can be changed. I'd recommend a Mac M3 :-)
>>
>> As tex is a single core process (ok, the os might delegate some file handling to other cores) it benefits from  jump in core speed. I use a 2017 laptop with a reasonable fast intel xeon.  I have a few docks spread round with different resolution monitors (1920x1200, 2560×1440, 4096×2160) and performance also depends on the connected monitor.
>>
>> I'd be curious to know how much these new processors impact performance over time because the ages of dohbling performance every year are past.
> 
> I mentioned the Mac M3 because it's not the cores that make the difference but the speed of the SSD. So reading the source and writing out the result, plus writing/reading any intermediate files is astonishingly fast on the Mac. Also the RAM is on the same die as the chip so RAM access speeds are high. Even if the app is single-threaded, the speed increases are significant - in fact especially when the app is single is threaded. :-)

File caching helps a lot indeed. Just compare

   context --make

after a reboot with the second or third time after that.

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	other threads:[~2024-01-19 18:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 17:24 [NTG-context] " Shiv Shankar Dayal
2024-01-18 17:47 ` [NTG-context] " Pablo Rodriguez via ntg-context
2024-01-18 18:40   ` Henning Hraban Ramm
2024-01-18 18:56     ` Shiv Shankar Dayal
2024-01-18 19:08       ` Mikael Sundqvist
2024-01-18 19:31       ` Hans Hagen
2024-01-18 23:34         ` Aditya Mahajan
2024-01-19  0:09           ` Hans Hagen via ntg-context
2024-01-19  0:33             ` Aditya Mahajan
2024-01-19  8:51               ` Hans Hagen
2024-01-18 22:15       ` Bruce Horrocks
2024-01-19  9:31         ` Hans Hagen
2024-01-19 10:00           ` Henning Hraban Ramm
2024-01-19 10:35             ` Taco Hoekwater
2024-01-19 10:49             ` Hans Hagen
2024-01-19 18:13           ` Bruce Horrocks
2024-01-19 18:30             ` Hans Hagen [this message]
2024-01-18 20:55 ` Gavin via ntg-context
2024-01-18 21:33   ` Joseph Wright

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=d05e771a-4d9d-4a7a-97d9-e214e15a6744@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --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).