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

[integ-tests] Improve scaling tests #6420

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

hanwen-pcluste
Copy link
Contributor

@hanwen-pcluste hanwen-pcluste commented Aug 29, 2024

  1. Use multiple AZs to get more capacity
  2. Use t3.medium for compute nodes. Because t3.medium has more capacity than c5.large.
  3. Use c5n.18xlarge (instead of c5.24xlarge) as head node because the bottleneck is the networking.
  4. Add more dynamic nodes to the clusters. Therefore, the tests are testing cluster with 150k dynamic compute nodes, in addition to scaling up / down with maximum 4000 nodes.

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

himani2411
himani2411 previously approved these changes Aug 29, 2024
@hanwen-pcluste hanwen-pcluste added the skip-changelog-update Disables the check that enforces changelog updates in PRs label Sep 3, 2024
@hanwen-pcluste hanwen-pcluste enabled auto-merge (rebase) September 3, 2024 13:05
1. Use multiple AZs to get more capacity
2. Use t3.medium for compute nodes. Because t3.medium has more capacity than c5.large.
3. Use c5n.18xlarge (instead of c5.24xlarge) as head node because the bottleneck is the networking.
4. Add more dynamic nodes to the clusters. Therefore, the tests are testing cluster with 150k dynamic compute nodes, in addition to scaling up / down with maximum 4000 nodes.

Signed-off-by: Hanwen <[email protected]>
@hanwen-pcluste hanwen-pcluste merged commit 4d25cde into aws:develop Sep 3, 2024
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-changelog-update Disables the check that enforces changelog updates in PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants