-
Notifications
You must be signed in to change notification settings - Fork 14
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
#2383 - Horizontal Autoscaler from replication controller to deployment config #2485
Conversation
@@ -225,18 +225,30 @@ objects: | |||
to: | |||
kind: Service | |||
name: ${NAME} | |||
- apiVersion: autoscaling/v1 | |||
- apiVersion: autoscaling/v2 |
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.
👍
devops/openshift/api-deploy.yml
Outdated
name: cpu | ||
target: | ||
type: AverageValue | ||
averageValue: '0.18' |
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.
Asking for my clarification, how did we arrive at this average value?
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.
90% of the CPU limit
name: memory | ||
target: | ||
type: AverageValue | ||
averageValue: "230M" |
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.
Same here.
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.
90% of the Memory limit
name: memory | ||
target: | ||
type: AverageValue | ||
averageValue: "1Gi" |
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.
I see higher numbers for form.io server than API for autoscaling, is this with consideration that form.io server is going to have lighter load than API?
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.
No, the averageValue is a percentage of the CPU and memory limits and here for formio, we have used the 50% as we used in the previous load testing iterations, this inturn helps for pods scaling without many requests failing.
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.
Got it. Thanks for explaining. If 50% then cpu must be 0.75 ?
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.
Yeah you are right, i did increased a bit and tested around so gave those value.
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 job 👍
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.
Looks good! Good job!
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. Just one really minor comment.
Let's talk about extending or having a second ticket to implement the scaleDown
behavior if needed.
Besides that, once deployed I would like to see the API autoscaling load test 😉
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.
👍 Thanks for the details
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
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.
Thanks for doing the changes, looks good 👍
Without HPA not properly assigned
With HPA properly assigned
Formio Load testing
WIth 2 pods it scaled up to 6 pods for 400 Vu
With 6 pods running the same sets of load for 400 Vu
With 6 pods running 300 Vu
With 6 pods running 200 Vu
With 6 pods running 100 Vu
With 2 pods running 100 Vu it started the 3rd pod