Comment 8 for bug 1290716

Still working on this, but from what I see, bsb, imagebuilder and test runner are the time consuming stages and we've already increased the bsb memory to 4G.

Along with increasing the memory/ cores/ scores we also need to see if we should impose timeouts for each stage. For now at least, it is impossible to see all possible reasons for a stage to wait/hang forever. As of rev365 I don't see any timeouts at least on ppa-assigner stage.

Increasing polling time from 60s-> 15s won't save us a lot in my view especially when we have stages taking time in minutes.

I am running consecutive tickets for the same package to compare the timing variations with the default configs of the deployment, not sure how many tickets we need to run to really spot a memory leak, but will keep running and later with some increased config values.