From our initial runs in #46651, we know that AOT'ing all of the test suites on the build machine is not realistic. Therefore, we should experiment with different approaches and pick the best one.
Produce one mega or several AppBundles
This approach allows us to AOT the framework libraries only once, potentially reducing the time spent AOT'ing to something more reasonable.
Shift AOT responsibility to helix
Allows us to parallelize the AOT effort since it would be done for each test suite that is run on helix.
Cache framework assemblies ahead of time
We precompile the framework assemblies before building tests and we share the object files w/ each test suite.
From our initial runs in #46651, we know that AOT'ing all of the test suites on the build machine is not realistic. Therefore, we should experiment with different approaches and pick the best one.
Produce one mega or several AppBundles
This approach allows us to AOT the framework libraries only once, potentially reducing the time spent AOT'ing to something more reasonable.
Shift AOT responsibility to helix
Allows us to parallelize the AOT effort since it would be done for each test suite that is run on helix.
Cache framework assemblies ahead of time
We precompile the framework assemblies before building tests and we share the object files w/ each test suite.