`juju status keystone` is 5x slower than `juju status`
Bug #1959352 reported by
James Troup
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
$ /usr/bin/time --verbose juju status keystone 2>&1 | grep Elapsed
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:25.04
$ /usr/bin/time --verbose juju status 2>&1 | grep Elapsed
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:04.46
$ juju controllers --refresh
Controller Model User Access Cloud/Region Models Nodes HA Version
foundations-maas* test-lma2-microk8s admin superuser maas_cloud/default 6 146 3 2.9.16
test-microk8s test-lma2 admin superuser test-microk8s/
$
Changed in juju: | |
status: | New → Triaged |
importance: | Low → Medium |
To post a comment you must log in.
This will be due to leaning heavily on the internal model cache for full status.