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 benchmarking pipeline #10738

Merged
merged 4 commits into from
Jan 15, 2025
Merged

Add benchmarking pipeline #10738

merged 4 commits into from
Jan 15, 2025

Conversation

kshyju
Copy link
Member

@kshyju kshyju commented Jan 14, 2025

Fixes #10727 & #10728

Adding a pipeline to execute benchmarks, scheduled to run nightly while allowing manual triggers. For nightly runs, the results are stored in a database, which serves as the source for plotting data on a Power BI dashboard. Each build also generates a JSON file containing the results, which is published as an artifact.

The benchmarks currently target two applications: one utilizing ASP.NET Core integration and the other based on the HttpRequestData API (Worker application).

Sample run: https://azfunc.visualstudio.com/internal/_build/results?buildId=197031&view=results

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

  • Backporting to the in-proc branch is not required
    • Otherwise: Link to backporting PR
  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • My changes do not require diagnostic events changes
    • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
  • I have added all required tests (Unit tests, E2E tests)

Additional information

Additional PR information

@kshyju kshyju requested a review from a team as a code owner January 14, 2025 00:32
eng/ci/templates/official/jobs/run-benchmarks.yml Outdated Show resolved Hide resolved
eng/ci/templates/official/jobs/run-benchmarks.yml Outdated Show resolved Hide resolved
eng/ci/templates/official/jobs/run-benchmarks.yml Outdated Show resolved Hide resolved
eng/ci/templates/variables/crank.yml Outdated Show resolved Hide resolved
tools/Crank/BenchmarkApps/DotNet/HelloHttpNet9/global.json Outdated Show resolved Hide resolved
eng/ci/templates/official/jobs/run-benchmarks.yml Outdated Show resolved Hide resolved
@kshyju kshyju requested a review from jviau January 15, 2025 05:54
@kshyju kshyju force-pushed the shkr/crank-on-1es-pool-agent branch from d060bef to 37ed31f Compare January 15, 2025 16:58
@kshyju kshyju merged commit 09f4edd into dev Jan 15, 2025
9 checks passed
@kshyju kshyju deleted the shkr/crank-on-1es-pool-agent branch January 15, 2025 18:20
@kshyju kshyju linked an issue Jan 29, 2025 that may be closed by this pull request
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.

Validate benchmark execution flow on Windows Setup nightly benchmark runs
3 participants