Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reducing Managed Libraries Testing Infrastructure Size #45126

Closed
3 tasks
steveisok opened this issue Nov 23, 2020 · 4 comments
Closed
3 tasks

Reducing Managed Libraries Testing Infrastructure Size #45126

steveisok opened this issue Nov 23, 2020 · 4 comments
Assignees
Labels
area-Infrastructure-mono tracking This issue is tracking the completion of other related issues.
Milestone

Comments

@steveisok
Copy link
Member

steveisok commented Nov 23, 2020

We need to optimize libraries testing infrastructure to work better with testing scenarios which involve AOT. Per our previous findings, we are right now around over 20 MB for most of them.

Approximate libraries size per single test suite/file
Android ~22.6MB (12.5MB compressed)
iOS ~22.6MB
Wasm ~15.6MB

We would like to get to about 2MB per test suite to make the whole testing faster and less demanding of resources. It takes at least 30 min now to compile a single 15 MB trimmed Wasm test suite.

Work Items

  • Resolve testing framework to be trimming safe
  • Enable aggressive trimming for all dependencies
  • Consider removing legacy non-netcoreapp dependencies

Update

We were able to significantly reduce the infrastructure by aggressively trimming out assemblies not being used. Our primary use case for this was to help build AOT for wasm to reduce the time it took to build the .wasm file.

Similarly, we had reduced the size for Android, but we had not investigated significantly for iOS yet.

I think the rest of this work should be pushed to 7.0.0

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Nov 23, 2020
@Dotnet-GitSync-Bot
Copy link
Collaborator

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@steveisok steveisok added area-Infrastructure-mono and removed untriaged New issue has not been triaged by the area owner labels Nov 23, 2020
@ghost
Copy link

ghost commented Nov 23, 2020

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

We need to optimize libraries testing infrastructure to work better with testing scenarios which involve AOT. Per our previous findings, we are right now around over 20 MB for most of them.

Approximate libraries size per single test suite/file
Android ~22.6MB (12.5MB compressed)
iOS ~22.6MB
Wasm ~15.6MB

We would like to get to about 2MB per test suite to make the whole testing faster and less demanding of resources. It takes at least 30 min now to compile a single Wasm test suite.

Work Items

  • Resolve testing framework to be trimming safe
  • Enable aggressive trimming for all dependencies
  • Consider removing legacy non-netcoreapp dependencies
Author: steveisok
Assignees: -
Labels:

area-Infrastructure-mono

Milestone: -

@jkotas
Copy link
Member

jkotas commented Nov 23, 2020

cc @ViktorHofer

@marek-safar marek-safar added the tracking This issue is tracking the completion of other related issues. label Nov 24, 2020
@marek-safar marek-safar added this to the 6.0.0 milestone Nov 24, 2020
@mdh1418 mdh1418 modified the milestones: 6.0.0, 7.0.0 Jul 27, 2021
@mdh1418
Copy link
Member

mdh1418 commented Jul 27, 2021

We were able to significantly reduce the infrastructure by aggressively trimming out assemblies not being used. Our primary use case for this was to help build AOT for wasm to reduce the time it took to build the .wasm file.

Similarly, we had reduced the size for Android, but we had not investigated significantly for iOS yet.

I think the rest of this work should be pushed to 7.0.0

@steveisok steveisok modified the milestones: 7.0.0, 8.0.0 Aug 5, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Sep 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-mono tracking This issue is tracking the completion of other related issues.
Projects
None yet
Development

No branches or pull requests

5 participants