GitLab

In Qt 6, the Default style was renamed to Basic, and the style that is
used by default now depends on which platform the application is run
on.

Previously the Default (now Basic) style was used by default.
So, restore the Basic style as the default. This ensures consistent
results should the default ever change again.

Task-number: QTBUG-88672
Change-Id: If96dd9cccd5fd05256221991bfacb4ae7bd3a1c1
Reviewed-by: Daniel Smith <Daniel.Smith@qt.io>
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>

Add support for building qmlbench with CMake

Change-Id: I85fd6ec6ef39beed8a8e067e121ddbca29b50bad
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>

The table was filled with the same one number, leading to significantly
different visual results compared to 5.15, because tests relying on
random number generation for item positions placed all 1000 or so items
to the exact same position in the scene.

Amends 01a08c32

Change-Id: I817de76b7142b68751b801ca9891d2afc7234acf
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

Use qmlRegisterAnonymousType since qmlRegisterType with 0 params
is deprecated.
Use QRandomGenerator instead of qrand()

Change-Id: Ic25c445fa8a9e08147093ea40f1b87f4067ef8c1
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

Change-Id: I97482601d942db565ef760177a8df09c2c4edd87
Reviewed-by: Andy Nichols <andy.nichols@qt.io>

Fixes: QTBUG-85063
Change-Id: I7c6aa2b39994aa5c87d121e96b362d6f8b428387
Reviewed-by: Christian Strømme <christian.stromme@qt.io>

Its constructor needs a QDate and QTime, not just a QDate.

Change-Id: Id61995f84ecf7fd83645fcaac114c376001068ee
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Change-Id: I712e2867e0906690ffdbee5565ff3da1ec9c9ae9
Reviewed-by: Daniel Smith <Daniel.Smith@qt.io>

Provide documentation on how benchmark files are constructed, along
with some usage examples.

Change-Id: Ica3d12ece98e8c1f37d0290bbdf6671c91e539c1
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

These are already removed in dev.

Change-Id: I1614d821f5320a27d0b83743e1389a5c91d15464
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>

Task-number: QTBUG-76229
Change-Id: I0c6d4c576075c9677af19c89756953cf21456f75
Reviewed-by: Michael Brasser <michael.brasser@live.com>

Change-Id: I76bad16f97871aaa3d7238c5e13189ccccc441d2
Reviewed-by: Daniel Smith <Daniel.Smith@qt.io>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>

Fails to build with XCode 10 otherwise. Probably missing the
enablement of C++14 or something. But for now just stick with
C++11.

Change-Id: I80845e3fb965b5781fd281f3d758cc5517b9e89f
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

Change-Id: I01be0574d6a09abe44336bcbe01ab6360396321f
Task-number: QTBUG-75585
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

    main.cpp:161:69: error: no matching function for call to ?Result::Result(<brace-enclosed initializer list>)?
             differencesInPercent << Result{testName, differenceInPercent};

Change-Id: I5cbc5495b42dd074fefa4b4e3db1b6d95b3586a0
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

Change-Id: I7a21c214e302a5b2422185659e261db11374f62c
Reviewed-by: Erik Verbruggen <erik.verbruggen@qt.io>
Reviewed-by: Michael Brasser <michael.brasser@live.com>

Change-Id: I1f984d2290aa78904b5a61e18e6439438291fb99
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@qt.io>

Change-Id: I47c04a1c5a3b90d7989d20992cbb0b3592dc9632
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>

Change-Id: If91b39f75e2215a4af125a226fa4b82086f3bd46
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

Erik noted that the test here is actually broken, but rather than change
the benchmark, let's add a working one alongside it.

Change-Id: I68058bedcc9760c86a600d5d34da0f8147062692
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

Mention that higher frames for the frame-count shell is better, lower
CoV is better, etc.

Change-Id: I33daa2ae168c7e64d59eb418f4e9df7232e24fce
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>

Change-Id: I5a4243b194611003e2b0a25a160d557c7f6d954f
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>

When we were bucketing results to try get better stability, this used to
give information about that. This was removed in f2ef76ce,
but this text remained. Remove it to avoid confusion.

Change-Id: I6a175807d920c3fe750b08b592bc412200c9a002
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>

Change-Id: I1497464741bbeb4f8ca680f9aeac95166aa81eb4
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>

Amends ab770345.

Change-Id: I4975e74113a6b28d4f36fc5cb1545496dd225ac3
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>

<cmath> needs to declare the math functions in the std namespace. Optionally it
can also put them in the global namespace, but for example the standard library
for QNX 6.6 does not do so.

Change-Id: Ie4d15d419d7a93c1c04d2b6982dba740d522740a
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>

Some tests, where the static count was set to 20000 would collect
all items along a diagonal line. It seems as if the reason for this
was that QML would evaluate all Xs first and then all Ys, and since
the static count was an exact multiple of the size of the
pregenerated array, the multiplier for X and Y would be the same,
so they would gather along the diagonal.

By setting the size of the array we make this unlikely (tests
with static count 20002 will still encounter the issue, but we
have none of those.)

Change-Id: I2d1df3c17f270a185e73e53d4ec9e2b56ddc799d
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>

In Qt 5.10 we introduce a new QRandomGenerator which is now
used by Math.random(), and there are signs that this is
significantly slower than qrand() which was used before. So
much so, that it is visible in many of the qmlbench benchmarks.
Note that this is a theory based on local runs and analysis of
the graphs and still needs to be proven.

Regardless, the qmlbench benchmarks are not intended to be
benchmarking Math.random(), it is just used to ensure the
positions tested are random. To eliminate that as a
possible cause for regressions, we instead introduce a
simple internal random function which just cycles through
a pregenerated array.

Note that this will reduce performance for all affected
tests on all branches of Qt, but it will hopefully reduce
the gap between Qt 5.9.0 and Qt 5.10.

Task-number: QTBUG-63922
Change-Id: Ib19c11323f38b23f9705e0d77a52a8a0f1157ac3
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>

Support for kerning/shaping was recently added to Qt Quick. These comparison
tests shows the performance benefit from disabling them, respectively.

Task-number: QTBUG-56728
Change-Id: I5a0cdf643b3f4d16980a832ecf9f79ebcad41d9b
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>

Custom properties on ShaderEffect can carry greater than normal
cost. Explicitly test a ShaderEffect with such a property.

Change-Id: Ib1344646585937f15a1c6c8b05806a4cea723994
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>

This allows you to override the default timeout of 10 minutes for
cases where one of the benchmarks is exceedingly slow, but you still
would like to collect the data for the others.

Change-Id: Ifcfc304a21e643d938e53bfd36ddaf6df6a8d515
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>

We should not count the warmup iterations in the overall number of
produced items. This seems wrong, and causes some confusion when
troubleshooting a broken test.

Note that a side effect of this change is that *all* results will now
drop by a value of 5 after this change is introduced.

Change-Id: Ib5e8a55411b663180f9d1a1a2a1df651bf0e4dc5
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>

This doesn't really have much point now that the split process mode has
stabilized

Change-Id: Ia88935b427d56ede40448d76bda7dbb261016827
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>

Change-Id: I00620d034c4d640e6f4a23ac1c890eec159067ad
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>

This had only a cosmetic effect of printing subprocess output with extra
linebreaks, but since it's not hard to fix, let's do that.

Change-Id: I5a81be5c29df84a5632fe2599ac31f35ae7e2f0f
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>

Change-Id: I07e675ff8acf7741e8a299b28f170624fccbdf13
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>

These still weren't directly comparable (as they have different count
figures), and the change has been causing significant confusion when
examining results.

At the same time, we introduce apparently regressed QObject array benchmark as
a new test so we can track improvements in that area.

This reverts commit 45da7843.

Change-Id: Id76a0a3ca1bfea2ec18a88a8ffe2cca985992142
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>

This approach is valid, but it's essentially a coin toss as to whether
onTChanged or the Timer fires first, so some tests may still tick a
little too long with the Timer based approach.

Change-Id: Ic0d53b60cea7cabf87cd9bd8ad13b8d8bc8727b1
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>

We call quit(), but some tests may be executing QML for a bit longer,
not respecting the quit flag. Tear down the engine so that the quit
happens sooner. This fixes e.g. some of the animation tests running a
bit longer after measurement is over.

Change-Id: Ie05aff3d962d537c7f5d05a53f2de12522e9035d
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>

It's too slow to be of much use as-is on TX1 (even on the cheapest possible
workload, EarleyBoyer takes 3 minutes, and gives a very low result). So
let's leave this for manual runs for the time being, and perhaps rethink how we
run them in the future.

Change-Id: I5f5eaf7443d7b55cebec670747a600ddf91c05d1
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>