Comment 5 for bug 1097015

On Wed, Jan 30, 2013 at 10:41:28PM -0000, Paul Collins wrote:
> Unfortunately this environment is as small as it can be; there are no
> disconnected clumps of unrelated services.
>
> We've worked around it in a couple ways. We're learning to limit scope
> where we can, and we've added a wrapper so that a bare "juju status"
> will read from a cached copy if it's considered recent enough.
Please consider upstreaming this into juju-jitsu?

> FWIW, we've deployed more subordinates since the original report and the
> run time is now up to around 6 minutes.
>
> --
> You received this bug notification because you are a member of Canonical
> Server Team, which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/1097015
>
> Title:
> "juju status" slows down non-linearly with new units/services/etc
>
> Status in juju:
> Confirmed
>
> Bug description:
> We have a large-ish Juju environment (with MAAS): 33 machines, 10
> primary services. Previously, "juju status" on this environment took
> about 10 seconds. After adding a simple subordinate charm to all
> primary services, it now takes 1 minute 47 seconds for "juju status"
> to complete.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1097015/+subscriptions
>

--
Mark Mims, Ph.D.
Ubuntu Server Team
Canonical Ltd.
<email address hidden>
+1(512)981-6467