The model cache is an unfortunate artifact which doesn't carry its weight - it is expensive to set up and keep in sync. In fact, it is currently only used to read app/unit status values for the juju status command, and provide logging config for a model. Both of these can be done by querying the model in the db directly.
In the main branch, we have removed it entirely. I wonder if we should backport this removal to 2.9.
The model cache is an unfortunate artifact which doesn't carry its weight - it is expensive to set up and keep in sync. In fact, it is currently only used to read app/unit status values for the juju status command, and provide logging config for a model. Both of these can be done by querying the model in the db directly.
In the main branch, we have removed it entirely. I wonder if we should backport this removal to 2.9.