zsb/fidc-backtest-engine
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(perf): record combined risk and series storage Backtest release

Browse Source
This commit is contained in:
boris
2026-09-14 11:13:50 +08:00
committed by boris
parent 665653c3fe
commit 93de28d369
2 changed files with 48 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/selection-risk-plan-performance-20260914.md
+25 -7
View File
@@ -2,7 +2,8 @@
## Status
Candidate tested, not deployed. The change removes selection calls that have
Published to Backtest in the combined 665653c/501f6d0 release described below.
The change removes selection calls that have
no possible effect under the current frozen policy. It does not disable any
configured rule, execution-day check or strategy expression. Engine time falls
slightly in the measured cases; this is not the solution to the main remaining
@@ -11,9 +12,9 @@ data construction cost and is not a general whole-backtest speedup claim.
The independent [intraday-clock counterexample](intraday-clock-causality-20260914.md)
was subsequently resolved by business-main work and published in the clock and
81acc54 callback releases. That correction is not attributed to this candidate.
Current published Backtest uses e81bf47/81acc54; the measurements below retain
their earlier c98 baseline. Complete manual-replay integration and publication
of this performance candidate remain open. Source d5b682c6 remains frozen;
Current published Backtest uses 501f6d0/665653c; the measurements below retain
their earlier c98 baseline. Complete manual-replay integration remains open.
Source d5b682c6 remains frozen;
research and signal work stay paused. No trading operation was submitted.
## Evidence Leading to the Change
@@ -112,9 +113,10 @@ Prioritize direct typed-column reuse during daily snapshot and DataSet
construction; approximately five seconds of preparation remain in these warm
cases. Do not skip normalization, NULL, adjustment or date/uniqueness checks.
Source cold-query and contract-validation latency remain separate tasks under
the Source freeze. The earlier cache-boundary candidate still needs its missing
cold/same-window acceptance, and this combined candidate has no HTTP publication
gate yet. Financial PIT, minute-clock behavior, signal lifecycle and UI factor
the Source freeze. The cache-boundary candidate later passed its conditional
cross-window/full-input gate and the combination passed daily HTTP publication;
neither establishes cold or universal performance. Financial PIT, broader minute
behavior, signal lifecycle and UI factor
condition acceptance are not claimed complete.
- Candidate engine: d2aa16a2f0064297d0d8c931060646d66422e9d4.
@@ -126,3 +128,19 @@ condition acceptance are not claimed complete.
- HTTP diagnostic: /srv/fidc/canonical/run/research/http-phase-profile-20260914.
[Verified acceptance summary](evidence/selection-risk-plan-20260914/acceptance.json).
## Combined Release
After merging engine 665653c, 860 core / 448 runner / 119 API tests and six
additional new-process replays passed. The guarded official workflow deployed
Backtest only, then nine HTTP runs matched their respective canonical/store
baselines. A multi-strategy sequence proved actual immutable DataSet hit counts
0/1/2/3/4 with distinct strategy results and repeatable trend results. Default
90-day cleared-DataSet HTTP mean 13.646 before versus 13.740 seconds after does
not demonstrate a general latency gain.
The active root /srv/fidc/canonical/build/factor-reserve-20260913 is protected
from reuse/cleanup. Source, paused research, trading services and all execution
permissions remain unchanged. This does not activate the manual-replay module.
Actual identities, timings and evidence are maintained in
`/Users/boris/WorkSpace/fidc-backtest-service/docs/cache-boundary-planning-performance-20260914.md`.