Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

2017-01-17 Thread Zane Bitter
On 11/01/17 09:21, Zane Bitter wrote: From that run, total memory usage by Heat was 2.32GiB. That's a little lower than the peak that occurred near the end of Newton development for the legacy path, but still more than double the current legacy path usage (0.90GiB on the job that ran for that

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

2017-01-11 Thread Zane Bitter
On 06/01/17 16:58, Emilien Macchi wrote: It's worth reiterating that TripleO still disables convergence in the undercloud, so these are all tests of the legacy code path. It would be great if we could set up a non-voting job on t-h-t with convergence enabled and start tracking memory use over

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

2017-01-07 Thread Emilien Macchi
On Fri, Jan 6, 2017 at 5:41 PM, Zane Bitter wrote: > On 06/01/17 16:58, Emilien Macchi wrote: >> >> On Fri, Jan 6, 2017 at 4:35 PM, Thomas Herve wrote: >>> >>> On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote: It's worth

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

2017-01-06 Thread Zane Bitter
On 06/01/17 16:35, Thomas Herve wrote: Thanks a lot for the analysis. It's great that things haven't gotten off track. I tracked down most of the step changes to identifiable patches: 2016-10-07: 2.44GiB -> 1.64GiB - https://review.openstack.org/382068/ merged, making ResourceInfo classes

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

2017-01-06 Thread Zane Bitter
On 06/01/17 16:40, Hugh Brock wrote: Why would TripleO not move to convergence at the earliest possible point? We'll need some data to decide when the earliest possible point is :) Last time Steve (Hardy) tested it I believe convergence was looking far worse than legacy in memory usage, at a

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

2017-01-06 Thread Zane Bitter
On 06/01/17 16:58, Emilien Macchi wrote: On Fri, Jan 6, 2017 at 4:35 PM, Thomas Herve wrote: On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote: It's worth reiterating that TripleO still disables convergence in the undercloud, so these are all tests of

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

2017-01-06 Thread Emilien Macchi
On Fri, Jan 6, 2017 at 4:35 PM, Thomas Herve wrote: > On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote: >> tl;dr everything looks great, and memory usage has dropped by about 64% >> since the initial Newton release of Heat. >> >> I re-ran my analysis of

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

2017-01-06 Thread Hugh Brock
Why would TripleO not move to convergence at the earliest possible point? On Jan 6, 2017 10:37 PM, "Thomas Herve" wrote: > On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote: > > tl;dr everything looks great, and memory usage has dropped by about 64% > >

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

2017-01-06 Thread Thomas Herve
On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote: > tl;dr everything looks great, and memory usage has dropped by about 64% > since the initial Newton release of Heat. > > I re-ran my analysis of Heat memory usage in the tripleo-heat-templates > gate. (This is based on the

[openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

2017-01-06 Thread Zane Bitter
tl;dr everything looks great, and memory usage has dropped by about 64% since the initial Newton release of Heat. I re-ran my analysis of Heat memory usage in the tripleo-heat-templates gate. (This is based on the gate-tripleo-ci-centos-7-ovb-nonha job.) Here's a pretty picture: