Let the benchmark fixture be any size, so the scaling question can be asked
count is now a parameter: ./tools/benchmark-fixture.sh --count 20000 builds the folder the performance doc has been promising 5000 and 20000-file numbers for. The script validates the argument rather than quietly building the default folder, which is the failure mode that would otherwise waste a run. Verified with 1500 files and then removed.
This commit is contained in:
+1
-1
@@ -218,7 +218,7 @@ when a run ended, which is why the earlier numbers had to be copied mid-run.
|
||||
|
||||
| number | status |
|
||||
|---|---|
|
||||
| Folder open with 5 000 / 20 000 files | not measured: the fixture script counts to 1 000 |
|
||||
| Folder open with 5 000 / 20 000 files | not measured yet: `./tools/benchmark-fixture.sh --count 20000` builds that fixture, and the open/scroll numbers follow from re-running the same command |
|
||||
| Thumbnail paint while scrolling a photo grid | not measured: no test for it yet |
|
||||
| Any jank figure at all | not measurable here: this phone's `FrameTimingMetric` output is `frameCount` only, with no `frameDurationCpuMs` or `frameOverrunMs` |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user