Indeed, this is amazing stuff: good job, it's great to see so
I can't help but wonder about the bootstrap time: it goes up by 75s
(from 114s to 189s, or ~66% increase)? Do you perhaps have multiple
runs comparing just the bootstrap times to ensure it's related more to
the environment state (hardware, network, load) than changes in the
code? Is there any explanation for the difference in the number of
deployments done and models created in roughly the same time (46/946 vs
52/1092, 13/15% decrease)?
It might still be a trade-off worth accepting, and even if it'd be even
better with no trade-offs, it's fine as long as we know about it and
make sure that we evaluate the value/cost proposition for each case.
У чет, 13. 10 2016. у 09:39 +1300, Menno Smits пише:
> Christian (babbageclunk) has been busy fixing various memory leaks in
> the Juju controllers and has made some significant improvements.
> Chris (veebers) has been tracking resource usage for a long running
> test which adds and removes a bunch of models and he noticed the
> Take a look at the memory usage graphs here:
> Before: http://people.canonical.com/~leecj2/perfscalemem/
> After: http://people.canonical.com/~leecj2/perfscalemem2/
> Interestingly the MongoDB memory usage profile is quite different as
> well. I'm not sure if this is due to Christian's improvements or
> something else.
> There's possibly still some more small leaks somewhere but this is
> fantastic regardless. Thanks to Christian for tackling this and Chris
> for tracking the numbers.
> - Menno
> Juju-dev mailing list
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/l
Juju-dev mailing list
Modify settings or unsubscribe at: