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

Poor performance from decodeLenient #48

Closed
arnoblalam opened this issue Dec 30, 2014 · 1 comment
Closed

Poor performance from decodeLenient #48

arnoblalam opened this issue Dec 30, 2014 · 1 comment

Comments

@arnoblalam
Copy link

Hi:

I am trying to use Wreq to build a library for Iron.IO message queueing service. I seem to be having some performance issues (the code runs an order of magnitude slower than python). The issue is documented here: https://stackoverflow.com/questions/27696738/why-is-my-haskell-code-so-slow

Profiler output seems to reveal that the majority of time is spent in the decodeLenient (family) of functions. I believe these calls are coming from Wreq, or one of the libraries that Wreq uses (such as http-client or tls). I suspect the issue might be coming from the tls library, or some other library that is decoding Base64 data.

I am not sure how to troubleshoot this issue further...

@ret
Copy link
Contributor

ret commented Dec 30, 2014

Hi Arnob, reading the code in your stackoverflow question, it's likely that your tests spend time establishing a new connection for each request. Consider using a Session. See http://www.serpentine.com/wreq/tutorial.html#handling-multiple-http-requests.

@bos bos closed this as completed Dec 22, 2015
This issue was closed.
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

3 participants