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

[test] #15692

Closed
wants to merge 1 commit into from
Closed

[test] #15692

wants to merge 1 commit into from

Conversation

danielxiangzl
Copy link
Contributor

Description

How Has This Been Tested?

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

@danielxiangzl danielxiangzl added the CICD:run-forge-e2e-perf Run the e2e perf forge only label Jan 9, 2025
Copy link

trunk-io bot commented Jan 9, 2025

⏱️ 24m total CI duration on this PR
Job Cumulative Duration Recent Runs
rust-move-tests 13m 🟩
test-target-determinator 4m 🟩
check-dynamic-deps 2m 🟩🟩
rust-cargo-deny 2m 🟩
semgrep/ci 50s 🟩🟩
general-lints 26s 🟩
file_change_determinator 14s 🟩
file_change_determinator 12s 🟩
permission-check 7s 🟩🟩
permission-check 5s 🟩🟩
permission-check 4s 🟩
determine-docker-build-metadata 2s 🟩

settingsfeedbackdocs ⋅ learn more about trunk.io

This comment has been minimized.

Copy link
Contributor

github-actions bot commented Jan 9, 2025

✅ Forge suite realistic_env_max_load success on 6216b04637cedc3855a138d0383bb595552a6b45

two traffics test: inner traffic : committed: 14834.30 txn/s, latency: 2680.93 ms, (p50: 2700 ms, p70: 2700, p90: 2900 ms, p99: 3600 ms), latency samples: 5640320
two traffics test : committed: 100.00 txn/s, latency: 1582.68 ms, (p50: 1500 ms, p70: 1600, p90: 1700 ms, p99: 2000 ms), latency samples: 1820
Latency breakdown for phase 0: ["MempoolToBlockCreation: max: 1.356, avg: 1.256", "ConsensusProposalToOrdered: max: 0.291, avg: 0.288", "ConsensusOrderedToCommit: max: 0.306, avg: 0.298", "ConsensusProposalToCommit: max: 0.595, avg: 0.585"]
Max non-epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.53s no progress at version 1190 (avg 0.19s) [limit 15].
Max epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.53s no progress at version 2384377 (avg 0.53s) [limit 16].
Test Ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CICD:run-forge-e2e-perf Run the e2e perf forge only
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant