https://bugs.kde.org/show_bug.cgi?id=524780
--- Comment #6 from Ralf Habacker <[email protected]> --- I refined the measurements in KMyMoney so that `setHtml()` and `show()` are now measured only for their respective blocks. On the same host: setHtml() 3025 ms show() 5402 ms So the actual `QTextBrowser` rendering path takes about 8.4 seconds. This is very close to my standalone test with the same ~1.6 MB HTML document: QTextBrowser: setHtml: 2800 ms show: 5253 ms Thus the slowdown appears to be reproducible in KMyMoney itself and is almost entirely accounted for by `QTextBrowser`. The report generation outside of the browser does not appear to be the main bottleneck. For comparison, the QWebEngine test on the same host was: load: 2 ms show: 21 ms processEvents: 37 ms So the difference between the two approaches is very large on this system. The Debug and Release builds of KMyMoney also show essentially the same timings. -- You are receiving this mail because: You are watching all bug changes.
