Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CI perf summary #786

Merged
merged 13 commits into from
Jan 16, 2025
Merged

Add CI perf summary #786

merged 13 commits into from
Jan 16, 2025

Conversation

mtfriesen
Copy link
Contributor

@mtfriesen mtfriesen commented Jan 10, 2025

Description

Describe the purpose of and changes within this Pull Request.

Summarize all performance data in a CI run onto a single page.

Testing

Do any existing tests cover this change? Are new tests needed?

CI.

Documentation

Is there any documentation impact for this change?

No.

Installation

Is there any installer impact for this change?

No.

@mtfriesen mtfriesen changed the title WIP Add CI perf summary Jan 10, 2025
nibanks
nibanks previously approved these changes Jan 13, 2025
@mtfriesen mtfriesen marked this pull request as ready for review January 15, 2025 14:57
@mtfriesen mtfriesen requested a review from a team as a code owner January 15, 2025 14:57
Comment on lines +48 to +50
Average = $Metric.Value | Measure-Object -Average | Select-Object -ExpandProperty Average
Minimum = $Metric.Value | Measure-Object -Minimum | Select-Object -ExpandProperty Minimum
Maximum = $Metric.Value | Measure-Object -Maximum | Select-Object -ExpandProperty Maximum
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's cast these to integers to drop the fractions. They just make the table harder to read.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree they're ugly and need more work, but I don't want to cast away values that could be 0.x.

ScenarioName = $_.Key.ScenarioName
Platform = $_.Key.Platform
CommitHash = $_.Key.CommitHash
MetricName = $Metric.Key
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally, I don't think this is useful since all of them are the same (pps), but if you really need to keep it, I recommend using Units instead of MetricName.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll add more metrics later - we obviously should have CPU usage, and perhaps drops, memory usage, etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Different metrics may have the same units - e.g. CPU% and RAM% are both units of per cent.

[pscustomobject]@{
ScenarioName = $_.Key.ScenarioName
Platform = $_.Key.Platform
CommitHash = $_.Key.CommitHash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use the short hash instead of the full one?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that would be more readable formatting

@mtfriesen mtfriesen merged commit 5ab695b into main Jan 16, 2025
58 checks passed
@mtfriesen mtfriesen deleted the mfriesen/perf_summary branch January 16, 2025 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants