[ModelRunner]Add profile execute duration observation #996
+192
−124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it?
We need to observe the time consumed in each stage of inference (including pre-processing, model forward, etc.), without any performance loss.
Therefore, we use the event timestamp mechanism of the NPU to mark any stage during the execution of the NPU device (this marking operation is executed asynchronously, with no performance loss).
Additionally, we provide a blocking synchronization API
**pop_captured_sync**
to be called at an appropriate time, to print the time consumed in all observed stages.model_runner_v1.py file only changed 5 lines, all of which were
ProfileExecuteDuration()
calls, and nothing else was changed, while more changes were showed due to the alignment issue.Does this PR introduce any user-facing change?
Use env
VLLM_MODEL_EXECUTE_TIME_OBSERVE
to enable this featureHow was this patch tested?
Tested in deepseek model,Print like this: