| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
| |
Change-Id: I5eae1021f022e6cab6790c29abf80cbeecfdec4a
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
| |
Change-Id: Iabefd1817dd97485dad79f8cef4294fd4ca628c5
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
| |
Change-Id: I3786c613c096756f2da59a12b91448f25d670b6c
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
|
|
|
|
| |
Also remove delegates_canvas_image_immediate_with_context.qml -- this is
not the right place to test performance of this, let's limit ourselves
to creation for now.
Change-Id: Ic59dfdff7658130525fcd7d886b61897563a6d01
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
delegates_script was a little flawed in that it set color as a prop, and
then set it again in the script handler. Simplify this by using item
(not rect) to bypass rendering.
This also tests a lot less stuff, and is now directly comparable with
delegates_item, which is a nice bonus.
Change-Id: I09a45e6dc1df2ea4cd116060a52a631bbfb9e92e
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
| |
Change-Id: If185a15df4cb8aca312e8e16ea9cf6dd77ea39a0
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Some of our benchmarks don't have a meaningful performance indicator (in
that they won't ever really improve or regress on the percentage
figure), but are still of interest in that they let us know if a
particular feature is totally broken or not.
This flag lets us easily mark such tests for ease of discovery when
looking into results / implementation of benchmarks.
Change-Id: Icda0981ba32d9abe84a835c0ca6ccb8a01be374d
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
|
|
|
| |
These will allow us to make benchmarks more succinct without adding too
much complexity.
Change-Id: I5b38dfc388d1d56780eb107d36060d3e1c23cdea
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
|
|
|
|
| |
These are too slow to provide much meaningful data other than "don't use
QQC1", and they take valuable runtime away from more useful benchmarks.
Change-Id: I08504a8ad70aaace557dee7a17b63d325d9840f8
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
No rendering, just testing creation (and one test of fetching context).
We have multiple tests here because there are multiple configurations,
and I expect that as these are exposed, there are more than likely going
to be people using them.
Change-Id: Id20ebb07bb6039bdd20cb3f4ddd45c796a561c3f
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
|
|
|
|
|
| |
As expected, RegExpValidator is the slow one of the bunch (around 70%
slower than the others). Surprisingly, it looks like IntValidator might
be a tiny bit faster than DoubleValidator, but it's within margin of
error anyway.
Change-Id: I1a6ce9cf8eca1fc75d4122cc0ba6db5ad2e582c7
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The original purpose of this benchmark was a little muddled. It seems
like it was being used to test isolation clip (but we already have that
through changing_over_isolated{*}) and changing a single piece of text.
We can do this simpler, by stealing most of changing_texts'
implementation but changing the text binding. This way, we gain a
boolean test that tells us whether or not changing a simple text item is
"cheap" or not.
Change-Id: Ifd878b43e0ee6ee808784dddd12e30a8863191d8
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The original benchmark wasn't all that useful. It created a canvas for
every piece of text, which meant that it wasn't really a fair comparison
of methods against changing_texts.
At the same time, such a comparison isn't really useful anyway: Text is
always going to win. So, at the same time as we simplify that to make it
*just* about text rendering, move it to a new dedicated "canvas"
subfolder and rename it to make it clear that it's just benchmarking
text rendering.
In the future, we will likely want to add more canvas tests.
Change-Id: I63ff1bd53357e0ae397afe52cfb8381e5ae2456c
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
|
|
|
| |
Remove the use of Rectangle, it doesn't make much sense since the
anchors are what we are interested in here.
Change-Id: I4baecc6296d665e2ec11559dd24c22ccbf27556f
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
|
|
|
|
| |
These aren't really benchmarks of anything concrete, so having them does
not seem useful. Separate tests for e.g. width+height vs anchors
bindings will be added instead.
Change-Id: I6d5225d421529ade6c44e5c76e03b856ef2b4bd7
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
| |
|
|
|
|
|
|
|
|
| |
These numbers are way too low right now, which leads to noise on
variation. Decrease the total work to be done to get higher (less noisy)
numbers.
Change-Id: I05061a78c5689cb79b752f1cc38bc2a6fca115d7
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
|
|
We now have a slightly better setup:
benchmarks/ (root)
auto/ (all benchmarks for regression testing purposes)
changes/ (old changes benchmarks, may be subject to further change)
creation/
... many subdirs, per module or per type in some cases
js/ (old js tests)
manual/ (useful tests that are probably not useful in an automated way)
gputhroughput/ (useful for HW evaluation)
This should let us explicitly run tests that we want to run in an
automated fashion (good), and provides us with a bit more organization
to allow for much more tests without looking like a disorganized mess.
No new tests as yet, but they will come...
Change-Id: I93d04fca84a7f0f10999691ebe0719c80265c852
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
