SoftwareApp d243e1ba7b 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.

2026-10-17 16:13:47 +02:00

..

store-assets

M10: store assets - Plain Files naming, generated icon/feature graphic, listing copy

2026-10-14 17:47:02 +02:00

benchmark-fixture.sh

Let the benchmark fixture be any size, so the scaling question can be asked

2026-10-17 16:13:47 +02:00

benchmark-watch-install.sh

Record the first complete benchmark run, and what its numbers are not

2026-10-17 15:26:59 +02:00

make-code-map.py

Add a macrobenchmark module, and find out what the build was hiding

2026-10-17 09:45:36 +02:00

make-demo-library.py

Screenshots: demo-library generator, per-form-factor targets, listing notes

2026-10-14 17:52:40 +02:00

make-store-assets.sh

M10: store assets - Plain Files naming, generated icon/feature graphic, listing copy

2026-10-14 17:47:02 +02:00

make-store-screenshots.sh

Screenshots: 10-inch tablet set; guard against blank captures

2026-10-14 23:44:24 +02:00

measure-startup.sh

Test the interface as a user sees it, and let a debug build tell on itself

2026-10-17 09:23:11 +02:00

verify.sh

Add a macrobenchmark module, and find out what the build was hiding

2026-10-17 09:45:36 +02:00