Add caching layer to central-application-gateway to improve performance #150
Comments
koala7659
added
the
area/application-connector
|
This issue or PR has been automatically marked as stale due to the lack of recent activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /lifecycle stale |
kyma-bot
added
the
lifecycle/stale
|
This issue or PR has been automatically closed due to the lack of activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /close |
|
@kyma-bot: Closing this issue. In response to this:
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. |
|
This issue or PR has been automatically closed due to the lack of activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /close |
|
@kyma-bot: Closing this issue. In response to this:
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. |
Disper
removed
the
lifecycle/stale
|
This issue or PR has been automatically marked as stale due to the lack of recent activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /lifecycle stale |
kyma-bot
added
the
lifecycle/stale
|
This issue or PR has been automatically closed due to the lack of activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /close |
|
@kyma-bot: Closing this issue. In response to this:
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. |
Disper
removed
the
lifecycle/stale
|
This issue or PR has been automatically marked as stale due to the lack of recent activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /lifecycle stale |
kyma-bot
added
the
lifecycle/stale
tobiscr
removed
the
lifecycle/stale
Description
Application Gateway must cache Kubernetes API server calls to improve performance. The following objects data must be cached:
Added by @tobiscr on 2024-06-28 : It has to be proven that the Applicaton Connector Module is able to process > 30 requests per seconds without causing client side throttling by the Kubernetes client.
Reasons
Some experiments were performed to understand the performance characteristics of the Application Gateway. Mock target API deployed inside Kubernetes cluster was used to measure operations performed by the Application Gateway. The experiments were performed with ddosify tool.
Although Application Gateway uses Horizontal Autoscaling, the experiments revealed that the maximal number of request per second was much smaller than expected. Analysis shown that the problem is directly caused by long response time of Kubernetes API server calls.
Added by @tobiscr on 2024-06-28: The ACM is also used by the SAP IT store which require a higher throughput (>30req/sec) and the currently used old application connector (Kyma 2.15) isn't able to deal with such load.
Depends on
#118 - if load test shows we are performing well, adding a caching layer could become obsolete
The text was updated successfully, but these errors were encountered: