spring-cloud / spring-cloud/spring-cloud-gateway
Spring Cloud Gateway bottlenecks over network after the filters are executed
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Our spring cloud gateway gets very slow while under load, after debugging, we identified that the filters are executed on time, but just after the filter, requests are taking time to reach the destination server.
On doing some research, I came to know that netty might be the bottleneck. So need to understand if there are any configurations related to spring webflux or netty which needs to be set inorder to have better performance. Also if there are any such properties, please let me know how do I set them in sping.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points. Start by reproducing the gateway under load and comparing timing after filter execution through the destination server; inspect Spring WebFlux and Netty configuration, with completion requiring a confirmed bottleneck or specific setting and documented effect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend, networking, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100