[openstack-dev] [tripleo][heat] Heat memory usage in the TripleO gate: Ocata edition
jtaleric at redhat.com
Wed Mar 15 19:52:51 UTC 2017
On Tue, Mar 14, 2017 at 4:06 PM, Zane Bitter <zbitter at redhat.com> wrote:
> Following up on the previous thread:
> Here is the latest data, which includes the Ocata release:
> As you can see, there has been one jump in memory usage. This was due to the
> TripleO patch https://review.openstack.org/#/c/425717/
> Unlike previous increases in memory usage, I was able to warn of this one in
> the advance, and it was deemed an acceptable trade-off. The reasons for the
> increase are unknown - the addition of more stuff to the endpoint map seemed
> like a good bet, but one attempt to mitigate that had no effect and I'm
> increasingly unconvinced that this could account for the magnitude of the
> In any event, memory usage remains around the 1GiB level, none of the other
> complexity increases during Ocata have had any discernible effect, and Heat
> has had no memory usage regressions.
> Stay tuned for the next exciting edition, in which I try to figure out how
> to do more than 3 colors on the plot.
Nice work Zane! Thanks for this!
Can we start looking at CPU usage as well? Not sure if your data has
this as well...
>  https://review.openstack.org/#/c/427836/
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev