I would consider it more constructive to admit the existence of the bug and find a way look into the source code of luametatex, since `context --help` is obviously not a terribly complicated routine to investigate.
> On 29 Oct 2020, at 12:44, Sylvain Hubert <champignoom@gmail.com> wrote:
>
> I've just tried chromium which behaves a bit better but still experiences a sudden raise of cpu usage from <10% to >70% during ~1s.
> I've also noticed that, even without any browser running, each time after I compile a file with `context`, my terminal get stuck for ~1s.
> So I'm pretty sure this is a context bug, probably caused by unnecessary excessive disk operations or something.
But it seems to be a big problem only on your machine. What hardware are you running on? Is it a Raspberry PI?
Like any TeX-related program, ConTeXt does a fair bit of disk access while starting up, but I haven’t heard of that being an actual problem since the age of single-core CPUs. And it certainly should not have an effect on the CPU usage of any other program (it could affect system responsiveness, though).
Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________