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

Improved implementation. #1

Merged
merged 2 commits into from May 18, 2018

Conversation

Projects
None yet
2 participants
@ioquatix
Copy link
Contributor

ioquatix commented May 17, 2018

  • Use async-http which connect using HTTP/2 and also use persistent connection to reduce latency. First request is around 120ms, second request is around 25ms.
  • Directly use async-dns which is what RubyDNS implemented on top of. It's better except for one small hack which I will fix in async-dns.

To see more details about what's going on inside server, run like this:

RUBYOPT=-d ./server.rb

By using HTTP/2, only one connection is required to make many concurrent requests.

@ioquatix

This comment has been minimized.

Copy link
Contributor

ioquatix commented May 17, 2018

The resource creation part of the code was a bit of a kludge, so I made a feature request here https://bugs.ruby-lang.org/issues/14771

@wintu wintu merged commit e7eb9cc into wintu:master May 18, 2018

@wintu

This comment has been minimized.

Copy link
Owner

wintu commented May 18, 2018

Thank you for your improvement! I will study by referring to your code : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment