Comment 2 for bug 1677434

@Ryan Beisner,

We are aware of some minor memory leaks that could escalate when 2.1x deployment run untouched for a while. These leaks can impact performance. I think that restarting jujud may have been sufficient for juju to behave acceptably for the next couple of days. However, the fact that rebooting controller host improved performance as well seems to point in that direction.

We have addressed all known ones on 2.2x. For example, bug # 1635311, bug # 1671258, bug # 1651291, bug # 1634328, bug # 1587644, bug # 1581069, bug # 1649719 to name a few :D

Is there any chance, you could re-try with Juju 2.2-beta1 or even daily snap?
We believe you will not get the same results \o/