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

Benchmark Tests #2963

Open
manno opened this issue Oct 18, 2024 · 0 comments
Open

Benchmark Tests #2963

manno opened this issue Oct 18, 2024 · 0 comments

Comments

@manno
Copy link
Member

manno commented Oct 18, 2024

We want to measure how Fleet performs on a given system of clusters, for a set of tests.

For a future benchmark suite, create the first test. This can be a script or executable, a Go benchmark test, etc.
The test runs against a cluster and collects several measures.

It should create 5 GitRepo resources, which contain 2 bundles each. The bundles should be targeted at 5 downstream clusters.
This will deploy 50 applications. The applications contain a medium amount of normal sized resources, e.g. 10 each.

  • how long does it take for the git commit sha to show up in each GitRepo resource (duration seconds per repo)
  • how long till bundle is created (per bundle)
  • how long till bundledeployment is created (per bundledeployment)
  • how long till agent finished install (per helm release)
  • how long till gitrepo/cluster/clustergroup are updated
  • number of reconciles (from prometheus)
  • duration of reconciles (from prometheus)
  • overall duration
  • controllers memory usage before and after the test
  • the amount of resources on the control plane before and after the test

Output the results in a useful format, e.g. JSON.

Future Work

  • setup of test environment
  • more test cases, e.g. one gitrepo, 50 gitrepos, 100 clusters
  • measure the time it takes to update the Rancher UI
  • measure CPU usage
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant