Evaluate row storage against pinned EnTT in an isolated deterministic benchmark
This commit is contained in:
@@ -99,3 +99,22 @@ Registry digest:
|
||||
|
||||
The dev manifest pins this digest. This proves build/test/image delivery; Argo
|
||||
application mapping and Kubernetes Job completion remain unverified locally.
|
||||
|
||||
## M1.5 native ECS experiment
|
||||
|
||||
Opt-in target evo-ecs-experiment (EnTT4 pinned in ADR-0021), based on 1c6e6e1 plus
|
||||
this experiment's changes. MSVC Release contract checks passed, including 72
|
||||
seed/density/count combinations, hand-calculated arithmetic, canonical equality,
|
||||
restore continuation, retired-ID rejection, malformed snapshot checks and
|
||||
allocator balance. The final clang-tidy build/test passed after tightening the
|
||||
process-boundary diagnostic catch. MSVC ASan passed on the final source.
|
||||
Baseline Release CTest remained 5/5
|
||||
and format-check included the experiment. No simulation rule/golden changed.
|
||||
|
||||
Commands: configure release/analysis/asan with `-B build/ecs[-analysis|-asan]
|
||||
-DEVO_BUILD_ECS_EXPERIMENT=ON`, build target evo-ecs-experiment, then
|
||||
`ctest --test-dir <directory> -R ecs-experiment --output-on-failure`.
|
||||
Seven measured samples plus warmup are retained in results/ecs-msvc1944.jsonl;
|
||||
protocol, build observations and scope limits are in ECS_EVALUATION.md. The
|
||||
Linux experiment CI job is pending its first pushed run; no Linux experiment
|
||||
success is claimed yet.
|
||||
|
||||
Reference in New Issue
Block a user