Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
HttpClient very slow if response has content length
See original GitHub issueIf you change spinoco.fs2.http.internal.HttpClientApp to hit http://httpbin.org/html (content length 3741) it will constantly take 60 seconds to complete. Hitting http://httpbin.org/get (content length ~159) returns in the time you would expect. Chunked responses are unaffected.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
C# Slow response times with HttpClient compared to ...
Another possible cause of slowdowns when using HttpClient or WebRequest is setting ServicePointManager.DefaultConnectionLimit too low.
Read more >Using HttpCompletionOption to Improve HttpClient ...
This behaviour is true in the case where the response body uses either 'Content-Length' or chunked 'Transfer-Encoding' semantics. In those cases ...
Read more >Analysis of HTTP Performance Problems
How Slow Start affects HTTP. HTTP is hurt by slow start on both the client and server sides. Because the HTTP headers are...
Read more >HTTP Client performance when reading large multipart ...
HTTP client is slow reading large multipart messages. Consuming data from a WebService with a HTTP client is slow when the message is...
Read more >Axios vs. fetch(): Which is best for making HTTP requests?
Axios is not always an ideal solution; depending on your needs, there are sometimes better options for making HTTP requests.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, I was upgrading from 0.2.0-RC1.
Using a local version of fs2 that includes the fix from https://github.com/functional-streams-for-scala/fs2/pull/1090 resolves the problem.
I dont think we need to release a new version, users can just pop up fs2 in their dependencies, and it will work fine.