Comment 6 for bug 1097015

Martin Packman (gz) wrote :

Caused by juju doing operations that require client-to-bootstrap-node communication for every machine/unit/relation/something. Kapil landed a change that reduced the provider api roundtrips from one per machine to one in total a while ago:


Unfortunately this didn't help much, as the majority of the time is now spent in zookeeper communication which still has this issue.

As the new go version of juju replaces the underlying infrastructure with something else, it shouldn't suffer from the same issue. However we're due to do some scale testing to see exactly how it behaves for larger deployments.