-
Notifications
You must be signed in to change notification settings - Fork 2k
Performance test the various crossgen2 options #1821
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
Comments
The following table provides the sizes of the the various crossgen2 options discussed in #1791. These images were produced from 942d7ee by running
All sizes (MB) are the expanded image on disk |
@davidwrighton - you mentioned the following at #1775 (comment)
Are these size reduction changes checked in? Do you know what build of crossgen2 I should be trying to get? |
@richlander, @davidwrighton - When do we want @billwert to run some perf tests against these proposed options? What functional validation should we be doing? I have hooked up the docker tests which run and e2e app scenario with these new images. @billwert - Do you have the infrastructure in place to measure containerized app startup? In order to test the images do you need them published to a Docker registry? |
@MichaelSimons size reduction changes will require significant work. It will take a month or two once we are focussed on it. |
Also, we are actively working on the correctness of these larger composite images. At the moment, I have relatively little confidence in correctness, but that confidence should grow rapidly over the next month or so. |
This issue tracks the work to do performance testing on the various crossgen2 options discussed in #1791. The work to implement the Dockerfile is tracked under #1820.
The performance testing should include analyzing the startup time, execution time as well as analyze the size of the various images including the size of the shared layers.
The text was updated successfully, but these errors were encountered: