-
Notifications
You must be signed in to change notification settings - Fork 80
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
Use Typhoeus to help forked/threaded users #272
Conversation
Not sure if you guys want to do this, but I get much better stability in my resque-pool multi-worker application using Typhoeus. See my comments in drbrain/net-http-persistent#37 |
Also I'm using this on the 6.1.x branch so I can only give data from there, but I ported it over to 7.0.x and it looks to be working. |
I seem to remember benchmarking the two adapters and finding On Wednesday, November 16, 2016, Coveralls <[email protected]
|
So I did some quick benchmarking on OSX / Ruby 2.3.1 and it looks like Typhoeus is basically as fast or faster (at least on a normal https:// web connection). I didn't spend a lot of time optimizing, so it's very possible I left something out so definitely have a look. The configurable approach is probably ideal, but it might be a little bit before I can look at that, however. |
I'm all for Typhoeus if it's at least as fast. As for configuration, I wonder is it possible to configure the adaptor via the |
Closing in favor of #273 |
Fixes #241.
This pull introduces/changes:
Pings:
@cheerfulstoic
@subvertallchris