On 12 May 2015 at 11:35, Clint Byrum <cl...@fewbar.com> wrote: > Excerpts from Mike Bayer's message of 2015-05-11 15:44:30 -0700:
> Anyway, there is additional thought that might change the decision > a bit. There is one "pro" to changing to use pymsql vs. changing to > use threads, and that is that it isolates the change to only database > access. Switching to threading means introducing threads to every piece > of code we might touch while multiple threads are active. I agree. > It really seems worth it to see if I/O bound portions of OpenStack > become more responsive with pymysql before embarking on a change to the > concurrency model. If it doesn't, not much harm done, and if it does, > but makes us CPU bound, well then we have even more of a reason to set > out on such a large task. And yes. -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ 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