-
Notifications
You must be signed in to change notification settings - Fork 42
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
Option to configure timeout #183
Conversation
when can the binaries be available for download ? any estimate |
Soon, but for now you can use this links |
cheers |
Included into v0.9.8 |
Hi, I've added "--output-httout 30s" in the replay command. But I'm still seeing many timeout when replaying the requests. Server response time must be less than 30s. Do you have any clue on this? Thanks |
@ztd9071 can it be that your server can't handle such load and just dropping requests or hang more then for 30s? Also can you give output of running command above with: Thank you! |
@buger Thanks for checking this. I will double check if the requests are dropped by server side, I will try using --stats flag to see what happened. Thank you! |
@buger Another question for you. I've dumped 30 minutes' requests from server. When I replayed using 300x speed, I didn't find the replay ends in 6 seconds. Is there a speed limit when replay? Thanks |
Hi,
stats: Thank you! |
Thank you, can you try this binary? gor_connection-timeout-fix_x64.tar.gz The main change is that previously when you were setting timeout option; it was affecting only "read" timeout, but not "connection" timeout (which was one second by default). Now it set both timeouts.
There is no any limit, only your hardware, and tested app. |
Thank you! |
Tell me if it fixed the problem, thanks! |
Hi @buger Thank you! |
Now you can configure http-output timeout with
--output-http-timeout 30s
. By default it is 5s.