-
Notifications
You must be signed in to change notification settings - Fork 2
qml optimizations [CPP-818] #809
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
front end benchmarks seem to run a bit slower compared to main branch |
@keithel-qt can you review please? |
for (var idx in Constants.advancedImu.lineColors) { | ||
if (lineLegendRepeaterRows.itemAt(idx)) | ||
lineLegendRepeaterRows.itemAt(idx).children[0].color = Constants.advancedImu.lineColors[idx]; | ||
let imuLineColors = Constants.advancedImu.lineColors; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not that I have any way to validate my hunch but I imagine this originally would have only counted as a single "resolve" event.
Two thoughts:
|
manually benchmarking, this seems to do inconsistent ±1-2% cpu utilization, seems too little to actually know if this is improving |
Create a test tag to trial this on a low power machine: https://github.com/swift-nav/swift-toolbox/releases/tag/v4.1.4-qmlopt (still building) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eyeballing things there seems to be some improvement (maybe) but definitely doesn't seem to hurt anything
came across these pages for optimizations:
https://doc.qt.io/qt-6/qtquick-performance.html#resolving-properties
and
https://doc.qt.io/qt-6/qtquick-performance.html#property-bindings