<div dir="ltr">Here are a few --<div>instance_get_all_by_filters joins manually with </div><div>instances_fill_metadata --</div><div><div><a href="https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L1890">https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L1890</a></div></div><div><a href="https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L1782">https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L1782</a><br></div><div><br></div><div>Almost all instance query functions manually join with instance_metadata.</div><div><br></div><div>Another example was compute_node_get_all function which joined compute_node, services and ip tables. But it is simplified in current codebase (I am working on Juno)</div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 11, 2015 at 3:09 PM, Clint Byrum <span dir="ltr"><<a href="mailto:clint@fewbar.com" target="_blank">clint@fewbar.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Excerpts from Sachin Manpathak's message of 2015-08-12 05:40:36 +0800:<br>
<span class="">> Hi folks,<br>
> Nova codebase seems to follow manual joins model where all data required by<br>
> an API is fetched from multiple tables and then joined manually by using<br>
> (in most cases) python dictionary lookups.<br>
><br>
> I was wondering about the basis reasoning for doing so. I usually find<br>
> openstack services to be CPU bound in a medium sized environment and<br>
> non-trivial utilization seems to be from parts of code which do manual<br>
> joins.<br>
<br>
</span>Could you please cite specific examples so we can follow along with your<br>
thinking without having to repeat your analysis?<br>
<br>
Thanks!<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div>