Skip to content
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

Why zuul2 has a high delay under low pressure #627

Closed
weitongming opened this issue Sep 26, 2019 · 6 comments
Closed

Why zuul2 has a high delay under low pressure #627

weitongming opened this issue Sep 26, 2019 · 6 comments
Labels

Comments

@weitongming
Copy link

zuul version:2.1.3
architecture: zuul + tomcat7

solution 1:

Pressure measuring tool:jmeter with 1 thread
An tomcat http interface request takes almost 7ms , and the jmeter pressure measurement data is as follows:

image

When I forwarded this request through zuul2 ,i got almost 48ms latency .

image

what happend to zuul and why the latency of zuul is so high?

Situation has changed under high pressure:jmeter with 100 thread

tomcat:
image

proxy from zuul:
image

It seems that zuul did not cause any delay. But why zuul2 has a high delay under low pressure?

Can anyone tell me why and how to resolve this problem ,thansk.

@JustyouLs
Copy link

unbelievable!

@carl-mastrangelo
Copy link
Contributor

Sorry, we don't know what your code is doing. You'll need to either provide a reproducible case, or gather profiling information on your server to debug this further.

@weitongming
Copy link
Author

Actually,i just found an incredible thing.
In my zuul project ,there are several different filters for different uses。
If i override the needsBodyBuffered method extend from HttpInboundFilter ,like:
image
All the latency has gone , the jmeter pressure measurement data is as follows
proxy from zuul:
image
tomcat:
image
I can reproduce it with zuul 2.1.3 and any tomcat , it is amazing.

@carl-mastrangelo
Copy link
Contributor

@weitongming As I said, you'll need to bring some more evidence to debug this further. You can use YourKit, or Async Profiler, or another profiler to see what is happening differently in your server.

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Sep 29, 2024
Copy link

github-actions bot commented Oct 6, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants