Skip to content

Caching for Graal #954

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.

Sign up for GitHub

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

Jump to bottom
Open
masklinn opened this issue Oct 7, 2024 · 2 comments
Open

Caching for Graal #954

masklinn opened this issue Oct 7, 2024 · 2 comments
Assignees
@aparnajyothi-y
Labels
feature request New feature or request to improve the current logic

Comments

@masklinn
Copy link

masklinn commented Oct 7, 2024

I'm not sure how the actions/setup-python caching is supposed to work, but every graal action indicates that it's "not found in the local cache", leading to a 30~35s overhead over cpython and pypy builds every time, contributing to the cost of graal jobs quite significantly (which adds onto graal's own issues).
@masklinn masklinn added feature request New feature or request to improve the current logic needs triage labels Oct 7, 2024
@gowridurgad
Copy link
Contributor

Hi @masklinn,
Thank you for the feature request. We'll investigate it and come back to you with the details!

@aparnajyothi-y
Copy link
Contributor

Hello @masklinn, The actions/setup-python caching currently does not apply to GraalVM runtimes, which is why you're seeing repeated downloads and the associated overhead. Since GraalVM support was removed from hosted runners starting April 2023 (#7338), it is no longer pre-installed and must be fetched each time unless cached explicitly.

To mitigate this, you could consider:

Using setup-graalvm directly, which offers more granular control and may support caching improvements in the future.

Implementing a custom cache strategy for downloaded GraalVM builds using actions/cache.

We understand this overhead adds up, especially for CI jobs, and we’ve noted this feedback as a potential optimization area.
Please let us know in case of any further support needed

@aparnajyothi-y aparnajyothi-y self-assigned this Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aparnajyothi-y aparnajyothi-y

Labels
feature request New feature or request to improve the current logic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@masklinn @aparnajyothi-y @gowridurgad