Open newbie-02 opened 1 month ago
For example: inserting 1 character in a line with no special formatting in a 400k document causes 33 seconds of about 50% CPU load and 50% mem usage on a 3.2 GHz Xeon 4-core machine with 64 GB ram. In my opinion, that is considerable overkill. I think that concepts are used here that are not important for short texts, but do not scale well when the size of the texts increases. Evtl. AsciidocFX should have a hint in documentation up to which size / complexity one could expect it to work well, and where one goes into risk / slowness.
Too much expectations, there is no such work capacity / financial background to meet your expectations.
I use AsciidocFX with Mac which works smooth and never noticed a performance problem. I even don’t have a windows machine to check how that works on Windows.
sorry, this is a more complex question ... and about observations and assumptions rather than knowledge.
observing the fan of my computer and my 'CPU-meter' it looks that AsciidocFX is quite power intense ... I get the impression as if again and again the whole text is read and worked through, even if I only change one character in a word. And becomes slow in long documents.
That sounds counter-intuitive to the task to be performed.
Assume ... just assume ... AsciidocFX doesn't work that way as of now, and assume it could have better performance, less system load?