diff options
author | Maximilian Goldstein <max.goldstein@qt.io> | 2020-10-30 13:23:34 +0100 |
---|---|---|
committer | Maximilian Goldstein <max.goldstein@qt.io> | 2020-11-02 09:44:01 +0100 |
commit | 0a3b8a3cfa158f5004864dd2bb251baef6874230 (patch) | |
tree | 298ce6e6cdf6368151a02399fc77d0cdf3d6bd99 | |
parent | 76ad14f74fc49d53b90a07a045f52544dbcc589e (diff) | |
download | qtdoc-0a3b8a3cfa158f5004864dd2bb251baef6874230.tar.gz |
qmlapp/performance: Remove obsolete sections
Change-Id: I556578a1f51c18459db75a77606d6bf7c418d591
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
-rw-r--r-- | doc/src/qmlapp/performance.qdoc | 16 |
1 files changed, 2 insertions, 14 deletions
diff --git a/doc/src/qmlapp/performance.qdoc b/doc/src/qmlapp/performance.qdoc index efa6825c..a00d383b 100644 --- a/doc/src/qmlapp/performance.qdoc +++ b/doc/src/qmlapp/performance.qdoc @@ -476,14 +476,9 @@ sub-properties of a value-type is usually far less than the number of elements in a sequence), any increase in the number of bindings being re-evaluated needlessly will have a negative impact on performance. -\section2 Other JavaScript Objects +\section1 General Performance Tips -Different JavaScript engines provide different optimizations. The JavaScript engine -which \l {Qt Quick}{Qt Quick 2} uses is optimized for object instantiation and property -lookup, but the optimizations which it provides relies on certain criteria. If your -application does not meet the criteria, the JavaScript engine falls back to a -"slow-path" mode with much worse performance. As such, always try to ensure you -meet the following criteria: +General JavaScript performance considerations resulting from the language design are applicable also to QML. Most prominently: \list \li Avoid using eval() if at all possible @@ -880,13 +875,6 @@ There are some cases where manually invoking the garbage collector is acceptable this is explained in greater detail in an upcoming section), but in most cases, invoking the garbage collector is unnecessary and counter-productive. -\section3 Avoid complex bindings - -Aside from the reduced performance of complex bindings (for example, due to having to -enter the JavaScript execution context to perform evaluation), they also take up more -memory both on the C++ heap and the JavaScript heap than bindings which can be -evaluated by QML's optimized binding expression evaluator. - \section3 Avoid defining multiple identical implicit types If a QML element has a custom property defined in QML, it becomes its own implicit type. |