High Latency

[bmgante]

Hi all, I have ingress-nginx setup with 3 replicas (request of 750m cpu each).

The current consumed resources of each one is around 0.3CPU and 100MB memory.

I have multiple ingresses defined but only of them receives more traffic, +- 100 requests per seconds.

I have no errors but request latency for that ingress is around 1sec which seems to be too big. How can i manage to decrease latency? Ingress-nginx helm chart is deployed with default settings, just changed the number of replicas and the request resources.

The vector pod itself is working fine, consuming only 0,05CPU and 15MB memory.

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[github-actions[bot]]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

[stefkkkk]

Same here, horrible performance seeing, even with very light load on any apps: nodejs, php Sometimes they processing normally, but sometimes latency spikes goes arount 500ms-3 seconds! I'm not using limits for CPU, even more - disabled completly CPU CFS Quota on kubelet

nginx ingress controller is behind NLB, using default kubernetes AMI(Amazon Linux 2) TLS is terminating on NLB

[longwuyuan]

/kind support

None of the information provided is able to help a reader reproduce a latency problem or guess the small tiny important details of the environment.

If you are still tracking this, then edit the issue description and test on the latest release of controller, to answer the questions asked in the new bug report template.

/close

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to [this](https://github.com/kubernetes/ingress-nginx/issues/10162#issuecomment-2348311857): >/kind support > >None of the information provided is able to help a reader reproduce a latency problem or guess the small tiny important details of the environment. > >If you are still tracking this, then edit the issue description and test on the latest release of controller, to answer the questions asked in the new bug report template. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.