But it seems to be a big problem only on your machine I fail to see what this implies.
What hardware are you running on? Is it a Raspberry PI? No, it's Core i5 + 8G ram + ssd.
Like any TeX-related program, ConTeXt does a fair bit of disk access while starting up. But none of the other TeX-related programs causes such a problem here.
And it certainly should not have an effect on the CPU usage of any other program. Indeed it should not have such an effect, so it failed to avoid what I should have avoided, and that's why it's a bug to be discovered and eliminated.
On Thu, 29 Oct 2020 at 13:56, Taco Hoekwater
On 29 Oct 2020, at 12:44, Sylvain Hubert
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
___________________________________________________________________________________