On 12/01/2022 17:30, Stefan de Konink wrote:
If you're seeing degraded performance on large documents, it's likely
another issue with quadratic runtime. Fixing such issues algorithmically
should typically yield much better results than trying to work around them
with multi-threading.
What can I do to identify these thing in a usable way? Would a profiler help
in this case?
Yes, profiling is usually the quickest way to see which part of the code is
causing performance issues. Then you could try to isolate the problem and come
up with a test case where doubling the input size results in quadrupling the
execution time or shows other superlinear behavior.
Nick
_______________________________________________
xml mailing list, project page http://xmlsoft.org/
xml@gnome.org
https://mail.gnome.org/mailman/listinfo/xml
