The extension dependencies tab is very costly in term of job status cache

By default the job status cache size is 50.

When loading the extension details in the UI the status of all dependencies and backward dependencies is loaded. when there is a lot of backward dependencies having their own status it can very quickly fill the cache. It also make loading the extension UI potentially slow (because you might have to parse a lot of job statues) while you don't care about the dependencies most of the time.

The following use case for example is very expensive:

• extension A installed explicitly on root
• extension B depends on A and is installed explicitly on 50+ wikis

-> every time the extension A is displayed the statuses of extension B fill the cache

Another issue is that when you upgrade A you can be stuck if calculating the upgrade plan is fast enough because the install plan won't be found in the cache (because it will be ditched out by the dependencies).

Some possible fixes:

• stop loading the status for the dependencies and the backward dependencies
• improve the UI to no reload the whole thing all the time
• store the install plan so that it's loaded from filesystem even if not in the cache anymore