-
Notifications
You must be signed in to change notification settings - Fork 16
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
Performance Test workload (2) #199
Conversation
Benchmark Result
Current status
|
545a749
to
cc45bae
Compare
cc45bae
to
5df8323
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Thanks a lot @louiseschmidtgen! Overall LGTM, just some minor comments and questions. Feel free to ignore the nits.
name: secret-{{.Replica}} | ||
type: Opaque | ||
data: | ||
password: Zm9vb29vb29vb29vb29vbwo= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⚡ echo "Zm9vb29vb29vb29vb29vbwo=" | base64 -d
fooooooooooooooo
if ">" in " ".join(command): | ||
command_str = " ".join(command) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The shlex.join doesn't work with special characters so if my command has a ">" in it I am doing a regular join.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests look like they work with the interesting redirects + background exec calls. Let's ship it. We can pull it back together with a library at some point perhaps
Performance Test Workload
There are two load tests:
On the cluster an api-intensive job is launched using kube-burner.
This test creates configmaps and secrets and deletes them.
While the load test runs, pidstat is used to get metrics on CPU, MEM, IO reads and writes and output those files for each node.
This is the start of such a metrics file:
This PR should be merged after #197
Note for reviewers
Popen is necessary to run the metrics collection command in the background.