-
Notifications
You must be signed in to change notification settings - Fork 8
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
go: use fasthttp instead of net/http. This should reduce http server … #6
Conversation
…influence on the test
Have you measured what you gain from using fasthttp instead of net/http? I did some tests and it looks like the high latency is due to the following issue:
Source: golang/go#15847 (comment)
Source: golang/go#14812 (comment) |
|
I know fasthttp and its advantages in terms of not allocating memory. I'm just wondering if you have measured the gain, before asking the project owner to merge this PR, because my guess is that the high latency is mostly caused by the issue described by Austin Clements in my comment above. |
Below are
|
No worries, I'll definitely try this out once I get back home! :) |
@valyala Thanks for sharing your results! You're right about I checked on my machine, using Here are my results using
And my results using
With 3 threads and 333 connections, Go performs almost like OCaml. But with 3 threads and 33 connections, Go still performs a lot worse than OCaml, even when using |
Added the new reports and images. Seems like the running time of 60s might not be enough to accurately measure Go now at least for the 333 client version, so it might need to be increased to 5 minutes. |
…influence on the test