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.

Sign up for GitHub

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

Jump to bottom

Assess scalability of CAPZ using ASO vs. Azure SDK #3547

Closed
1 task done
Tracked by #3402
nojnhuh opened this issue May 8, 2023 · 4 comments
Closed
1 task done
Tracked by #3402

Assess scalability of CAPZ using ASO vs. Azure SDK #3547

nojnhuh opened this issue May 8, 2023 · 4 comments
Assignees
@mtougeron
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Milestone
v1.16

Comments

@nojnhuh
Copy link
Contributor

nojnhuh commented May 8, 2023 •
edited
Loading

At a high level, we should ensure CAPZ's current scalability limits do not drop below what's acceptable once we start using ASO. Scalability in this case refers to the total volume of clusters (in number and in size) that CAPZ can manage.

Limits to look out for include:

  • CPU/memory usage (of both CAPZ and ASO)
  • Azure API rate limits

Dependencies
Preview Give feedback
  1. ASO service: groups #3524
    nojnhuh
This was referenced May 8, 2023
Closed
Closed
@dtzar dtzar added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Aug 3, 2023
@dtzar dtzar mentioned this issue Aug 3, 2023
Closed
@mtougeron
Copy link
Member

/assign

This was referenced Oct 13, 2023
Closed
Closed
Closed
Closed
Closed
@dtzar
Copy link
Contributor

dtzar commented Dec 12, 2023

@mtougeron - could you please share what progress you might have made in the performance testing of CAPZ space? I'm starting to get more requests from people in this space in general.

@dtzar dtzar added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Mar 9, 2024
@mboersma
Copy link
Contributor

We should establish a performance bsaeline here, such as "what's the smallest management cluster that can support a large number of worker clusters?" etc.

@mboersma mboersma added this to the v1.16 milestone May 16, 2024
@mboersma mboersma moved this to Todo in CAPZ Planning May 16, 2024
@jackfrancis
Copy link
Contributor

Closing to focus on general performance measurements

@github-project-automation github-project-automation bot moved this from Todo to Done in CAPZ Planning May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mtougeron mtougeron

Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
CAPZ Planning
Archived in project
Milestone
v1.16
Development

No branches or pull requests
5 participants
@mtougeron @mboersma @jackfrancis @dtzar @nojnhuh