2026-09-04 测试机实跑发现:改造后 `写入=` 取的是整个批循环的墙钟(tWrite 设在循环外), 而批内预取也在这个循环里 ⇒ 两段重叠、`场景+预取+写入` 远大于 `总计`。 实测那轮 `写入=1,243,665ms` 里有 **983,448ms 其实是预取**,真正写库只有 260,217ms。 误导性的度量比没有度量更糟 —— 而这几个数正是判断本次改造成败的依据: 照原样读会得出"写入段劣化 886%"的结论,实际是 105%(而且那一轮的对照本身也不干净, 未被修改的场景段同时涨了 49%,说明外部条件不同,当轮数据不足以判劣化)。 改:批内单独累计 writeMs(只含 runPool + createMany),与 prefetchMs 不重叠。 顺带修掉一个死变量:初版声明过 writeMs 但从未使用(tsc 没报是因为没开 noUnusedLocals)。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| dto | Loading commit data... | |
| engine | Loading commit data... | |
| recall-debug | Loading commit data... | |
| agent-roster.service.ts | Loading commit data... | |
| assignment-facts.ts | Loading commit data... | |
| assignment-proposal.service.ts | Loading commit data... | |
| assignment-signals.ts | Loading commit data... | |
| assignment.controller.ts | Loading commit data... | |
| claim-guard.ts | Loading commit data... | |
| cohort-attributes.service.ts | Loading commit data... | |
| cohort-filter.ts | Loading commit data... | |
| dispatch-guard.ts | Loading commit data... | |
| execution-callback.service.ts | Loading commit data... | |
| execution.service.ts | Loading commit data... | |
| plan-assignment.service.ts | Loading commit data... | |
| plan-event.recorder.ts | Loading commit data... | |
| plan-label.service.ts | Loading commit data... | |
| plan-label.sql.ts | Loading commit data... | |
| plan-rearrange.service.ts | Loading commit data... | |
| plan.controller.ts | Loading commit data... | |
| plan.module.ts | Loading commit data... | |
| plan.service.ts | Loading commit data... | |
| rearrange-facts.ts | Loading commit data... | |
| rearrange.controller.ts | Loading commit data... | |
| reason-temperature.sql.ts | Loading commit data... | |
| recall-suppression.ts | Loading commit data... | |
| recycle-scheduler.service.ts | Loading commit data... |