Skip to content
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

Include number of failures #9

Open
kelunik opened this issue May 18, 2020 · 3 comments
Open

Include number of failures #9

kelunik opened this issue May 18, 2020 · 3 comments

Comments

@kelunik
Copy link
Contributor

kelunik commented May 18, 2020

The different clients show different success rates for me, so I guess it would be helpful to include the number of successful vs. unsuccessful requests. It might also be a good idea to investigate the different error rates.

@Insolita
Copy link
Owner

Insolita commented May 18, 2020

Yes, it make sense. Different clients have a little bit different timeout logic. For ex. guzzle has separated connection timeout.
And at whole the main reason for lower speed is to follow redirects. But it is necessary for many cases

@Insolita
Copy link
Owner

BTW, Amphp client currently is most greedy for memory usage

@kelunik
Copy link
Contributor Author

kelunik commented May 20, 2020

@Insolita Indeed. With FFI enabled and nghttp2 installed, it's much lower, but still high.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants