kyma
kyma copied to clipboard
kyma-project
Low request/second response when ApiRule is set to noop
Description
Creating a simple service using an NGINX docker image with a simple static website, and an ApiRule with default configuration, we get around 160-170 request/second for a 3 cluster nodes ( 4cpu + 16GB ram ). Setting the ApiRule to allow increases the req/sec considerable 800-900/req/seq
Expected result
We should get higher requests/s with default settings. ( 2000-3000 req/sec )
Actual result
We get 160-170 request/second for a 3 cluster nodes ( 4cpu + 16GB ram ).
Steps to reproduce
Create a simple service using an NGINX docker image with a simple static website, and an ApiRule with default configuration.
Use wrk to test the response time:
wrk -t12 -c128 -d100s --latency https://art-explorer.prod.kymart.shoot.canary.k8s-hana.ondemand.com/
Troubleshooting
Please keep in mind that the default setup of istio (istio-ingressgateway and proxy) will limit the number of req/s your tests will yield. Please retry your tests on the production profile, which has been tuned to provide better performance.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
![kyma-stale-bot[bot] avatar](https://avatars.githubusercontent.com/u/39153523?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed due to the lack of recent activity.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed due to the lack of recent activity. /lifecycle rotten
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
- After 60d of inactivity,
lifecycle/staleis applied - After 7d of inactivity since
lifecycle/stalewas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Close this issue or PR with
/close
If you think that I work incorrectly, kindly raise an issue with the problem.
/lifecycle stale
This issue or PR has been automatically closed due to the lack of activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
- After 60d of inactivity,
lifecycle/staleis applied - After 7d of inactivity since
lifecycle/stalewas applied, the issue is closed
You can:
- Reopen this issue or PR with
/reopen - Mark this issue or PR as fresh with
/remove-lifecycle stale
If you think that I work incorrectly, kindly raise an issue with the problem.
/close
@kyma-bot: Closing this issue.
In response to this:
This issue or PR has been automatically closed due to the lack of activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
- After 60d of inactivity,
lifecycle/staleis applied- After 7d of inactivity since
lifecycle/stalewas applied, the issue is closedYou can:
- Reopen this issue or PR with
/reopen- Mark this issue or PR as fresh with
/remove-lifecycle staleIf you think that I work incorrectly, kindly raise an issue with the problem.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.