Open Stack

On Tue, 2014-02-25 at 10:45 +0000, John Garbutt wrote:
> 
> As a heads up, the overheads of DB calls turned out to dwarf any
> algorithmic improvements I managed. There will clearly be some RPC
> overhead, but it didn't stand out as much as the DB issue.
> 
> The move to conductor work should certainly stop the scheduler making
> those pesky DB calls to update the nova instance. And then,
> improvements like no-db-scheduler and improvements to scheduling
> algorithms should shine through much more.
> 
Although DB access is sure the key for performance, but do we really
want to pursue conductor-based scheduler?

--jyh