On 9 May 2015 at 15:02, Mike Bayer <mba...@redhat.com> wrote: > On 5/9/15 6:45 AM, John Garbutt wrote: >> >> I am leaning towards us moving to making DB calls with a thread pool and >> some fast C based library, so we get the 'best' performance. Is that a crazy >> thing to be thinking? What am I missing here? Thanks, John > > I'd like to do that but I want the whole Openstack DB API layer in the > thread pool, not just the low level DBAPI (Python driver) calls. There's > no need for eventlet-style concurrency or even less for async-style > concurrency in transactionally-oriented code.
Sorry, not sure I get which DB API is which. I was thinking we could dispatch all calls to this API into a thread pool: https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py I guess an alternative is to add this in the objects layer, on top of the rpc dispatch: https://github.com/openstack/nova/blob/master/nova/objects/base.py#L188 But that somehow feels like a layer violation, maybe its not. Is that similar to what you where thinking? Thanks, John __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
