-
Notifications
You must be signed in to change notification settings - Fork 20
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
feat(ai-navigator): set proper resource limits and requests #1585
feat(ai-navigator): set proper resource limits and requests #1585
Conversation
I've ran 25 bot users which are constantly asking questions against the service on the daily and it was inside the limits with a good margin. It never went above 0.008 CPU usage and memory wasn't really much affected, it stayed <30MB observed in our Grafana Dashboard. * Closes D2IQ-99125
This repo has @d2iq-mergebot integration. You can perform the following commands by submitting a comment. Submit a comment with content "@d2iq-mergebot help" to view more detailed help text and examples. Be sure the have a look at the mergebot documentation, too.For help using mergebot, please refer to the README file here: https://github.com/mesosphere/mergebot/blob/main/README.md |
Pull Request Test Coverage Report for Build 6183341991
💛 - Coveralls |
d337226
to
cf5af84
Compare
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
* fix: remove empty config map * feat(ai-navigator): set proper resource limits and requests I've ran 25 bot users which are constantly asking questions against the service on the daily and it was inside the limits with a good margin. It never went above 0.008 CPU usage and memory wasn't really much affected, it stayed <30MB observed in our Grafana Dashboard. * Closes D2IQ-99125 * chore: set limits == requests (cherry picked from commit d97ee74)
* fix: remove empty config map * feat(ai-navigator): set proper resource limits and requests I've ran 25 bot users which are constantly asking questions against the service on the daily and it was inside the limits with a good margin. It never went above 0.008 CPU usage and memory wasn't really much affected, it stayed <30MB observed in our Grafana Dashboard. * Closes D2IQ-99125 * chore: set limits == requests (cherry picked from commit d97ee74)
…ests (#1585) (#1597) feat(ai-navigator): set proper resource limits and requests (#1585) * fix: remove empty config map * feat(ai-navigator): set proper resource limits and requests I've ran 25 bot users which are constantly asking questions against the service on the daily and it was inside the limits with a good margin. It never went above 0.008 CPU usage and memory wasn't really much affected, it stayed <30MB observed in our Grafana Dashboard. * Closes D2IQ-99125 * chore: set limits == requests (cherry picked from commit d97ee74) Co-authored-by: Max Strübing <mxstrbng@gmail.com>
What problem does this PR solve?:
I've ran 25 bot users which are constantly asking questions against the
service on the daily and it was inside the limits with a good margin.
It never went above 0.008 CPU usage and memory wasn't really much
affected, it stayed <30MB observed in our Grafana Dashboard.
Which issue(s) does this PR fix?:
https://d2iq.atlassian.net/browse/D2IQ-99125
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Checklist