[Interest] Qt 5.12 Beta 3 slows down ext Javascript library (RSA encrypt)

Tomasz Olszak olszak.tomasz at gmail.com
Tue Nov 6 06:30:47 CET 2018


Still there is a performance regression somewhere and while the C++
solution is most performant the cause of this regression can hit other
parts of Qml stack.
Ekke do you use prebuilt binaries or do you compile them yourself?

If you compile yourself you can bisect and find the cause. Not many
patches landed in qtdeclarative in 5.11.3:

4a886753a Accessible: Return StaticText if there is no explicit role set
0f0ed2070 At least warn when triggering a rendering limitation
614d16d6f Doc: place more importance on not binding to x/y/width/height
7f57472e2 Warn, don't crash during nested delivery of mouse or touch presses
1ce94fc0f Qt Labs Settings: warn if failed to initialize internal
QSettings instance
7ca32bc41 qmlplugindump: Remove sigsegv handler
453a3806a Document that aliases cannot point to attached properties
10095542d Fix crash in QQuickAnimatorProxyJob::sceneGraphInitialized()
9cb13a422 QQuickItem: document which events are accepted by default
074190902 Mark QML captured scope/context loads as having side effects
f27a16b7b Don't get confused about the grabber during replayDelayedPress
3bdb3c1d8 Amend TouchMouse::buttonOnDelayedPressFlickable to test delayed tap
934d93b91 YarrJIT: disable MatchResult decoding constructor on 64bit
ec1fdecef Add QQuickItemPrivate::updateOrAddItemChangeListener()
777cd6e9b Add QT_CONFIG(filesystemwatcher) guard for include
039a28468 Fix Integrity OS allocator memory attributes
4441cefd7 Doc: Remove wrong ';' from Q_PROPERTY example
8fd398c9d Prevent PathView's parent stealing mouse grab during double-flick


wt., 6 lis 2018 o 06:20 Thiago Macieira <thiago.macieira at intel.com> napisaƂ(a):
>
> On Monday, 5 November 2018 11:32:03 PST ekke wrote:
> > Thanks, Thiago for the hint - that was the first thing I tried, but
> > couldn't figure out HowTo make it work on Android and iOS.
>
> > unfortunately now with 5.12 Beta it slows down by 20x.
>
> Then get a 400x improvement by trying the C++ part again. OpenSSL is easy on
> Android, since you'll have to deploy it anyway alongside your application.
>
> On iOS and macOS, you shouldn't use OpenSSL. You should use Apple's API,
> whatever it is. Please consult Apple's website.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>
>
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest



More information about the Interest mailing list