You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since most requests go to the same servers, it would seem that Keep-alive and HTTP connection pooling would be extremely helpful for this library. Most of my application's delays are spent on urllib2 requests to the graph. Any chance of updating the code to use urllib3 or Requests that would likely speed up a query? In some benchmarks I've seen, they can be twice as fast.
Oh, and Requests support's Python 3, which may address this issue, since it appears most of it focuses on urllib queries.
The text was updated successfully, but these errors were encountered:
I would really like the library to one day support Requests (for the reasons you mentioned), but have not found time to work on it. I took a short look at it previously, but was discouraged by the fact that it did not support Google App Engine. This seems to no longer be the case, though.
Since most requests go to the same servers, it would seem that Keep-alive and HTTP connection pooling would be extremely helpful for this library. Most of my application's delays are spent on urllib2 requests to the graph. Any chance of updating the code to use urllib3 or Requests that would likely speed up a query? In some benchmarks I've seen, they can be twice as fast.
Oh, and Requests support's Python 3, which may address this issue, since it appears most of it focuses on urllib queries.
The text was updated successfully, but these errors were encountered: