You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Summary
Fixes#11771.
`model_execution_start_ms` and `model_execution_end_ms` were exposed in
the LLM runner stats but stayed at zero because the runner never
recorded the model execution boundary. This change shares the generation
stats with `TextDecoderRunner`, measures calls to `Module::execute()`,
resets the values for each generation, and emits them in the observer
JSON.
### Test plan
- Reproduced on current `main` with a Qwen3.5-0.8B PTE: both model
execution timestamps were `0`.
- `test_runner --gtest_filter='StatsTest.*'` (2 passed)
- `test_runner --gtest_filter='RunnerTest.*'` (12 passed)
- `test_runner --gtest_brief=1` (116 passed, 2 skipped because optional
PTE test fixtures were not supplied)
- Built `llama_main` and ran the same Qwen3.5-0.8B PTE twice. Both runs
reported nonzero model execution timestamps ordered within the inference
interval; for example, `1784555623119 <= 1784555624620`.
cc @larryliu0820@mergennachin@cccclai@helunwencser@jackzhxng@digantdesai
0 commit comments