On Tue, Apr 10, 2012 at 03:59:19PM -0700, Richard Su wrote:
One bottleneck we have is in the Conductor calls to Image Warehouse.
It is unclear to me if the proposed Image Factory API changes will
help to alleviate it or if it is one of their goals.
Finding specific attributes in the template is currently one of the
costlier operations we make. Since the template is immutable once it
is uploaded by Conductor, I wonder if we should consider caching some
of the more frequently used attributes like operating system,
version, and architecture (used in /conductor/pool_families). Adding
the attributes into a Conductor model is an alternative.
I had nearly forgotten about this, but you're right. This would _really_
benefit from caching.
Although, I wonder if
https://www.aeolusproject.org/redmine/issues/3084
would obviate the need for this. If not, this is definitely worth
exploring.
-- Matt