>
> ...
>
> We have most of the responsive nature of Juju is driven off the watchers.
> These watchers watch the mongo oplog for document changes. What happened
> was that there were so many mongo operations, the capped collection of the
> oplog was completely replaced between our polled watcher
Hi folks,
We had another scale test today to analyse why the controller CPU usage
didn't fall away as expected when the models were removed.
I'll be filing a bunch of bugs from the analysis process, but there is
one bug that is, I believe, the culprit for the high CPU usage.
Interestingly e
