diff options
| author | Ville Voutilainen <ville.voutilainen@qt.io> | 2021-12-01 13:14:20 +0200 |
|---|---|---|
| committer | Ville Voutilainen <ville.voutilainen@qt.io> | 2022-01-04 11:12:11 +0000 |
| commit | c9d84ead801960601870240e36478468c2a28b82 (patch) | |
| tree | fbd2c6ae0466ecfce032e5eebca10d02dcae7bf3 /src/benchmarks/manual/gputhroughput/README.md | |
| parent | 6d298da7cda85b35aa22c68aac55fdb6513e68eb (diff) | |
Use a resource file for benchmarks, and add some Android goodies and fixes
Task-number: QTBUG-94148
Change-Id: I7cc0b1ade676c4f7f963915315c00e317582e56f
Reviewed-by: Daniel Smith <Daniel.Smith@qt.io>
Diffstat (limited to 'src/benchmarks/manual/gputhroughput/README.md')
| -rw-r--r-- | src/benchmarks/manual/gputhroughput/README.md | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/src/benchmarks/manual/gputhroughput/README.md b/src/benchmarks/manual/gputhroughput/README.md new file mode 100644 index 0000000..28800bb --- /dev/null +++ b/src/benchmarks/manual/gputhroughput/README.md @@ -0,0 +1,16 @@ +# gputhroughput + +These benchmarks test your GPU for the most part. The QML part is mostly there +to set things up and the benchmark will fill the graphics pipeline with enough +stuff to make it suffer. + +**Note**! These tests are only designed to be used with the sustained-fps shell. + +The purpose of these benchmarks is to give an indication how how much one can +expect to put on screen, and to decide how big the screen can actually be. +Especially in the embedded space where a low end chip may have to drive an HD +display, these tests can help to illustrate if the GPU is up to the task or not. + +Run them in --fullscreen to get the right numbers. 1 means your in trouble. 2 means +you can manage with a lot of work. 4 and above and you should be good shape, GPU-wise. + |