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

Changes for adding benchmark compare feature #4931

Merged
merged 1 commit into from
Aug 9, 2024

Conversation

rishabh6788
Copy link
Collaborator

Description

This PR:

  • Adds new job compare-benchmarks to run benchmark comparison between baseline and target run.
  • Updated existing benchmark-pull-request job to call compare-benchmarks job once it is successfully finished to also update the comparison results on the calling pull_request.

Issues Resolved

opensearch-project/OpenSearch#14826.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Copy link

codecov bot commented Aug 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.41%. Comparing base (408471b) to head (ed8ce10).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4931   +/-   ##
=======================================
  Coverage   92.41%   92.41%           
=======================================
  Files         197      197           
  Lines        6634     6634           
=======================================
  Hits         6131     6131           
  Misses        503      503           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@peterzhuamazon peterzhuamazon left a comment

Choose a reason for hiding this comment

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

  1. If someone triggers a benchmark in PR, seems like compare will auto trigger if success?
  2. benchmark has 24hr timeout while compare also have 24hr timeout, do we need this long period of time to run them?

Comment on lines 294 to 303
// Trigger compare-benchmarks job
build job: 'compare-benchmarks',
parameters: [
string(name:'BASELINE_TEST_EXECUTION_ID', value: "${benchmarkTestIds.baseline}"),
string(name:'BASELINE_TEST_EXECUTION_ID', value: "${benchmarkTestIds.contender}"),
string(name:'PULL_REQUEST_NUMBER', value: "${pull_request_number}"),
string(name:'REPOSITORY', value: "${repository}")
],
wait: false,
propagate: false
Copy link
Member

Choose a reason for hiding this comment

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

Spacing.

@rishabh6788
Copy link
Collaborator Author

  1. If someone triggers a benchmark in PR, seems like compare will auto trigger if success?
  2. benchmark has 24hr timeout while compare also have 24hr timeout, do we need this long period of time to run them?
  1. Yes.
  2. The benchmark job for certain workloads runs for 12-hr, and as the workloads increase in size can go up. But compare job should not take more than 10-15-mins to run, reduced timeout to 1-hr.

pullRequestNumber: "${pull_request_number}"
)
// Trigger compare-benchmarks job
build job: 'compare-benchmarks',
Copy link
Member

Choose a reason for hiding this comment

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

Nit: Possible of changing this to benchmark-compare to in sync with other benchmark workflow naming convention?

Thanks.

@rishabh6788 rishabh6788 merged commit 2765399 into opensearch-project:main Aug 9, 2024
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

2 participants