I think I have worked out the performance issues with eventlet and Requests with most of it being that swiftclient needs to make use of requests.session to re-use connections, and there are likely other areas there that we can make improvements.
Now on to expect: 100-continue support, has anyone else looked into that? -- Chuck On Fri, Apr 4, 2014 at 9:41 AM, Chuck Thier <cth...@gmail.com> wrote: > Howdy, > > Now that swift has aligned with the other projects to use requests in > python-swiftclient, we have lost a couple of features. > > 1. Requests doesn't support expect: 100-continue. This is very useful > for services like swift or glance where you want to make sure a request can > continue before you start uploading GBs of data (for example find out that > you need to auth). > > 2. Requests doesn't play nicely with eventlet or other async frameworks > [1]. I noticed this when suddenly swift-bench (which uses swiftclient) > wasn't performing as well as before. This also means that, for example, if > you are using keystone with swift, the auth requests to keystone will block > the proxy server until they complete, which is also not desirable. > > Does anyone know if these issues are being addressed, or begun working on > them? > > Thanks, > > -- > Chuck > > [1] > http://docs.python-requests.org/en/latest/user/advanced/#blocking-or-non-blocking >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev