You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why does the overall average response time for long connections (keep-alive) exceed that for short connections (close) in performance tests? Why is this?
average response time:
14.01ms > 9.76ms (keepalive > close)
Expected Behavior
Long connections perform better than short connections.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is there an existing issue for this?
Kong version (
$ kong version)kong 3.5.0
Current Behavior
Why does the overall average response time for long connections (keep-alive) exceed that for short connections (close) in performance tests? Why is this?
average response time:
14.01ms > 9.76ms (keepalive > close)
Expected Behavior
Long connections perform better than short connections.
Steps To Reproduce
command:
1.post 500KB,connection:keepalive
wrk -t8 -c16 -d1m -s post.lua --latency --timeout 5s http://10.129.9.39:5074/user (kong)
wrk -t8 -c16 -d1m -s post_close.lua --latency --timeout 5s http://10.129.9.39:5074/user (kong)
client post 500KB, server returned the string "ok".
post.lua
post_close.lua
Anything else?
wrk:

iftop:

500kb-json.zip
Beta Was this translation helpful? Give feedback.
All reactions