Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
qtwebkit 5.212 bad performance compared to qtwebkit from branch 5.6
eugen_1102 last edited by
i am using a qtwebkit based browser on a Beaglebone Black with a 7" display to display a web based (on target running) HMI.
I build the image using yocto (version 1.8 "fido") and i am using QT version 5.6.3 (meta-qt branch krogoth).
qtwebkit is currently build from the 5.212 branch of https://github.com/qt/qtwebkit.
Now i did some test and compiled qtwebkit from branch 5.6 instead of 5.212.
The rest of the yocto env did not change.
After comparing the two qtwebkit based browsers i realized that the branch 5.6 based browser has much better performance.
Not only the initial loading time is nearly the half of the time that qtwebkit 5.212 based browser needs.
Its also the performance when using the hmi (switchnig menus for example).
Can somebody explain this behaviour.
I assumed that the newer qtwebkit 5.212 should be faster.
Is it because of my old yocto version?
Or because of the old QT Version?
Thanks in advance
eugen_1102 last edited by eugen_1102
i have some progress now.
the performance is much better after i forced to build qtwebkit as "Release" version.
I was not aware about the fact that yocto builds the debug version "by default."
id did the change with extra line in my yocto bbappend file:
EXTRA_OECMAKE += " -DCMAKE_BUILD_TYPE=Release"
i found this advice in the meta-arago repo from TI.
In the commit message you can see that this was advice of a QT Engineer: http://arago-project.org/git/meta-arago.git?p=meta-arago.git;a=commit;f=meta-arago-distro/recipes-qt/qt5/qtwebkit_%.bbappend;hb=7b53c802532b5da20c68b714326584af65483fef
@Konstantin-Tokarev: shouldn't this be a default setting in the current meta-qt5?
because when building qtwebkit from branch 5.6 (where qmake is used), the default settings is creating a release version of qtwebkit