<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 29, 2014 at 7:52 AM, Thierry Carrez <span dir="ltr"><<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Ihar Hrachyshka wrote:<br>
> Hi all,<br>
><br>
> there is a series of Neutron backports in the Juno queue that are<br>
> intended to significantly improve service performance when handling<br>
> security groups (one of the issues that are main pain points of<br>
> current users):<br>
><br>
</span>> - <a href="https://review.openstack.org/130101" target="_blank">https://review.openstack.org/130101</a><br>
> - <a href="https://review.openstack.org/130098" target="_blank">https://review.openstack.org/130098</a><br>
> - <a href="https://review.openstack.org/130100" target="_blank">https://review.openstack.org/130100</a><br>
> - <a href="https://review.openstack.org/130097" target="_blank">https://review.openstack.org/130097</a><br>
<span class="">> - <a href="https://review.openstack.org/130105" target="_blank">https://review.openstack.org/130105</a><br>
><br>
> The first four patches are optimizing db side (controller), while the<br>
> last one is to avoid fetching security group rules by OVS agent when<br>
> firewall is disabled.<br>
><br>
> AFAIK we don't generally backport performance improvements unless they<br>
> are very significant (though I don't see anything written in stone<br>
> that says so), but knowing that those patches fix pain hotspots in<br>
> Neutron, and seem rather isolated, should we consider their inclusion?<br>
><br>
> Should we come up with some "official" rule on how we handle<br>
> performance enhancement backports?<br>
<br>
</span>I personally think performance enhancements are off the table for stable<br>
backports. It's really a trade-off between exposing our users to<br>
regressions and fixing bugs, and performance enhancements IMHO fall<br>
below the bar.<br></blockquote><div><br></div><div>Would you not agree that there is some threshold at which bad performance becomes a blocking issue, just like any other bug? I think the problem is in determining where that threshold lies.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I'm adding that topic to the stable branch discussion at the summit, though.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Thierry Carrez (ttx)<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Openstack-stable-maint mailing list<br>
<a href="mailto:Openstack-stable-maint@lists.openstack.org">Openstack-stable-maint@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint</a><br>
</div></div></blockquote></div><br></div></div>