fix: exclude final metric sample when running with workload #570
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.
Summary
Fixes #569 - Prevents skewed mean metric values when collecting metrics for workloads.
When collecting metrics with a workload (e.g.,
perfspect metrics -- stress-ng --cpu 0 --cpu-load 60 --timeout 30), the final sample may be collected after or during workload completion. This captures the system transitioning from loaded to idle state. With short collections (e.g., 30 seconds = 6 samples), this single anomalous sample can significantly skew summary statistics.Changes
WithWorkloadfield toMetadatastruct - Tracks whether metrics were collected with a user-provided workload applicationWithWorkload = truewhen workload arguments are provided via--excludeFinalSample()method - Removes final timestamp's rows from all metric groups before computing summary statisticsSolution Approach
The implementation excludes the final timestamp's samples from summary statistics when
metadata.WithWorkloadis true. The full CSV with all samples is still preserved for users who want to perform advanced analysis.Testing
make checkpasses (format, vet, staticcheck, lint, vulnerabilities, tests)Test plan
perfspect metrics -- stress-ng --cpu 0 --cpu-load 60 --timeout 30