Github/littlefs
1
Fork 0
Code Actions Activity

runners: bench: Bumped sim up to 1 MiB + 1 hour + 128 MiB disk

Browse Source 
This gives us much more room for activities.

It makes sense to keep the test disk small: easier parallelization,
heavier emubd with more test features, and if you're running into space
issues in a test, that usually just means you need to be more creative
with how the test is setup.

But for benches, we're interested what happens when we throw a ton of
data at the system.

Also defaulted to noop erases. 0xff erases behave more predictably,
which is useful for testing. But for benching, less work is faster.
This commit is contained in:
Christopher Haster
2026-02-03 23:28:08 -06:00
parent 123b4fc038
commit fec5b36357
3 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
runners/bench_defines.h
+4 -2
View File
@@ -13,7 +13,7 @@
// preconfigured defines that control how benches run
#ifdef BENCH_DEFINE
// name value (overridable)
BENCH_DEFINE(DISK_SIZE, 1024*1024 )
BENCH_DEFINE(DISK_SIZE, 128*1024*1024 )
BENCH_DEFINE(DISK_GEOMETRY, 0 )
BENCH_DEFINE(READ_SIZE, DISK_MAP(READ_SIZE) )
BENCH_DEFINE(PROG_SIZE, DISK_MAP(PROG_SIZE) )
@@ -35,7 +35,9 @@
BENCH_DEFINE(FRAGMENT_SIZE, LFS3_MIN(BLOCK_SIZE/8, 512) )
BENCH_DEFINE(CRYSTAL_THRESH, BLOCK_SIZE/8 )
BENCH_DEFINE(LOOKGBMAP_THRESH, BLOCK_COUNT/4 )
BENCH_DEFINE(ERASE_VALUE, 0xff )
// don't bother simulating erases, this may be less realistic, but
// it's certainly faster!
BENCH_DEFINE(ERASE_VALUE, -1 )
BENCH_DEFINE(READ_WIDTH, DISK_MAP(READ_WIDTH) )
BENCH_DEFINE(PROG_WIDTH, DISK_MAP(PROG_WIDTH) )
BENCH_DEFINE(ERASE_WIDTH, DISK_MAP(ERASE_WIDTH) )