Controllers using 2.5x max memory in 3.7 compared to 3.6

[smarterclayton]

Controllers on 3.7 are using 2.5x the memory than a larger cluster on 3.6 (3.6 5gb @ 13k namespaces, 3.7 13gb @ 10k namespaces)

[enj]

I would be curious to know if #16986 helps with this since all listers were affected.

[mfojtik]

@smarterclayton this was because the job controller got wild, right? this was fixed and @derekwaynecarr have PR open upstream for generic quota.

[smarterclayton]

No, this was mostly because of garbage created by authorization.

…

On Wed, Nov 1, 2017 at 9:33 AM, Michal Fojtik ***@***.***> wrote: @smarterclayton <https://github.com/smarterclayton> this was because the job controller got wild, right? this was fixed and @derekwaynecarr <https://github.com/derekwaynecarr> have PR open upstream for generic quota. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16955 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABG_p2-xQP0pHkTBsEpMjZ2jZBO0mI-hks5syHMUgaJpZM4P_Zqy> .

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close