performance suite and upcoming
features (was: [nova] blueprint about
multiple workers)
Attila Fazekas afaze...@redhat.com wrote:
I see lot of improvements,
but cPython is still cPython.
When you benchmarking query related things, please try to
get the actual data from
:49 PM
Subject: Re: [openstack-dev] [all] SQLAlchemy performance suite and upcoming
features (was: [nova] blueprint about
multiple workers)
Mike Bayer mba...@redhat.com wrote:
Attila Fazekas afaze...@redhat.com wrote:
Hi,
I wonder what is the planned future
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Wednesday, March 4, 2015 11:30:49 PM
Subject: Re: [openstack-dev] [all] SQLAlchemy performance suite and upcoming
features (was: [nova] blueprint about
multiple workers)
Mike Bayer mba
Mike Bayer mba...@redhat.com wrote:
Attila Fazekas afaze...@redhat.com wrote:
Hi,
I wonder what is the planned future of the scheduling.
The scheduler does a lot of high field number query,
which is CPU expensive when you are using sqlalchemy-orm.
Does anyone tried to switch