re 6) The api-cache is a clear win. Api pipelining feels like its going to
entail some complexity for a win mostly on trivial cases, ie those where a
single api call is the usage. Else there are questions of what happens with
an error in this stack, what if a following op was conditional on a
previ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
> 5) So if we found a way to pipeline requests, and get rid of gaps,
> instead of taking 10 RTT, we could potentially get down to 5 RTT.
> (2 gaps, calling Upgrade + Login + SetEnvironmentConstraints
> immediately rather than waiting for response
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was curious, so I did some benchmarking of CLI performance. The good
news is that we're doing a lot better in Trunk than in 1.16, and we
have a clear win coming up.
For testing I just did:
time for i in `seq 10`; do juju set-constraints mem=4G; do
