Improve server performance by decreasing the number of Analysis context's created

[keertip]

We have seen the analysis server consume large memory such that it is rendered unusable.
#52447
#41793

Reducing the number of AnalysisContext's creates and used when analyzing user code will result in improvement of performance and memory usage.

Two arcs of work have been identified as a way to reduce the number of contexts

• support a monorepo workspace, based on changes to pub proposal #4022
• Support multi-option contexts #53876
  • move strictCasts bool field out of TypeSystemImpl analyzer: move strictCasts bool field out of TypeSystemImpl #53873

[srawlins]

Okie doke, P1 issue, any recent updates?

[pq]

Context work is waiting for #54858. Maybe @keertip can speak to the monorepo bits?

[keertip]

The monorepo work in the analyzer has landed and awaiting the pub work to be done so that it can be tested. Pub work is tracked in dart-lang/pub/#4127

[bwilkerson]

Any updates?

[pq]

Context work is still in progress. There are some bot failures I'm still trying to reproduce under test (#54858).

[bwilkerson]

Any updates?

[pq]

We're wating for https://dart-review.googlesource.com/c/sdk/+/362442 to fully make it through a flutter roll before we can turn on multi-option contexts (see #55413).

[pq]

22da6ed flips the bit for multi-option contexts, but we've reverted related changes twice so I think we want to let it bake for a few more days at least before declaring victory.

[bwilkerson]

Any progress?

I know that we're waiting for @keertip to test the monorepo support, but I believe the analysis options work is done. Is that correct?

[pq]

Yep. I think the analysis options work is done.