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

use gce runner for execution-performance benchmark #15300

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

aluon
Copy link
Contributor

@aluon aluon commented Nov 18, 2024

Description

Migrate the execution-performance workflow to using CE instances instead of using runners from our CI cluster

I'm using the related-sciences/gce-github-runner action to create and cleanup the instance. I forked this with some changes to make it work with our dev_setup.sh

How Has This Been Tested?

https://github.com/aptos-labs/aptos-core/actions/runs/11898685620/job/33396239201?pr=15300

Key Areas to Review

Type of Change

  • New feature
  • Bug fix
  • Breaking change
  • Performance improvement
  • Refactoring
  • Dependency update
  • Documentation update
  • Tests

Which Components or Systems Does This Change Impact?

  • Validator Node
  • Full Node (API, Indexer, etc.)
  • Move/Aptos Virtual Machine
  • Aptos Framework
  • Aptos CLI/SDK
  • Developer Infrastructure
  • Move Compiler
  • Other (specify)

Checklist

  • I have read and followed the CONTRIBUTING doc
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I identified and added all stakeholders and component owners affected by this change as reviewers
  • I tested both happy and unhappy path of the functionality
  • I have made corresponding changes to the documentation

Copy link

trunk-io bot commented Nov 18, 2024

⏱️ 1h 57m total CI duration on this PR
Slowest 15 Jobs Cumulative Duration Recent Runs
execution-performance / test-target-determinator 25m 🟩🟩🟩🟩🟩 (+2 more)
execution-performance / create-runner 20m 🟥🟩🟩🟩🟥 (+2 more)
rust-move-tests 13m 🟩
rust-move-tests 12m 🟩
rust-move-tests 12m 🟩
rust-cargo-deny 7m 🟩🟩🟩🟩
test-target-determinator 7m 🟩🟩
check-dynamic-deps 6m 🟩🟩🟩🟩
test-target-determinator 6m 🟩
rust-move-tests 3m
general-lints 2m 🟩🟩🟩🟩
semgrep/ci 2m 🟩🟩🟩🟩
create-runner 49s 🟩
file_change_determinator 48s 🟩🟩🟩🟩
file_change_determinator 26s 🟩🟩

🚨 1 job on the last run was significantly faster/slower than expected

Job Duration vs 7d avg Delta
execution-performance / test-target-determinator 3m 4m -23%

settingsfeedbackdocs ⋅ learn more about trunk.io

@aluon aluon requested review from geekflyer, perryjrandall and a team November 18, 2024 17:52
@aluon aluon marked this pull request as ready for review November 18, 2024 17:52
@aluon aluon requested a review from a team as a code owner November 18, 2024 17:52
@aluon aluon added the CICD:run-execution-performance-test Run execution performance test label Nov 18, 2024
steps:
- uses: actions/checkout@v4
with:
ref: ${{ inputs.GIT_SHA }}
if: ${{ inputs.IGNORE_TARGET_DETERMINATION || needs.test-target-determinator.outputs.run_execution_performance_test == 'true' }}

- uses: aptos-labs/aptos-core/.github/actions/rust-setup@main
- uses: aptos-labs/aptos-core./.github/actions/rust-setup@main
Copy link

Choose a reason for hiding this comment

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

There appears to be an extra period in the action path aptos-labs/aptos-core./.github/actions/rust-setup@main which will cause the action to fail. The correct path should be aptos-labs/aptos-core/.github/actions/rust-setup@main.

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CICD:run-execution-performance-test Run execution performance test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant