feat: add percentiles configuration for request lifecycle metrics reporting #295
+58
−48
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.
When benchmarking high-throughput inference servers with complex architectures involving multiple network hops (e.g., llm-d), we observed that ITL often converge to near-zero values at lower percentiles.
To analyze these scenarios effectively, we need the ability to define granular percentile breakpoints rather than relying on a fixed set of standard percentiles.
The functionality was verified by building the image and running benchmarks with custom percentile configurations.