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

Can the GraalVM Presubmit checks be faster? #2585

Open
diegomarquezp opened this issue Mar 15, 2024 · 1 comment
Open

Can the GraalVM Presubmit checks be faster? #2585

diegomarquezp opened this issue Mar 15, 2024 · 1 comment
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@diegomarquezp
Copy link
Contributor

These checks take usually ~35 minutes. I wonder if we can make them faster somehow.
image
image

@diegomarquezp diegomarquezp added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Mar 15, 2024
@mpeddada1 mpeddada1 self-assigned this Mar 18, 2024
@mpeddada1
Copy link
Contributor

mpeddada1 commented Mar 18, 2024

Adding some observations on times to understand where the delays are coming from:

From #2581

Building sdk-platform-java dependencies: 02:02 min
Showcase
Run showcase tests: 2 mins
Generate native image: 11 min
Run tests after native image build: 1 min

Monorepo - KMS
Run tests for KMS: 1 min
Generate native image: 10 mins
Run tests after native image build: <1 min

Monorepo - KMS Inventory
Run tests for KMS Inventory: <1 min
Generate native image: 10 min
Run tests after native image build: <1 min

Building the native images appears to be taking a majority of time.

One idea: The graalvm script first runs the showcase job and then the monorepo tests sequentially. There may be an opportunity for us to parallelize this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants