-
Notifications
You must be signed in to change notification settings - Fork 143
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
How to increase memory/cpu dedicated to container? #70
Comments
Why do you believe the Docker container started by the action uses less resources ? |
Sorry for not clarrifying, I used this action for some time on clojure-lsp to compile it to graalvm on aarch64, and the action take ~1h-15m while other builds take 10-15mins |
This action uses QEMU to emulate the target CPU architecture and QEMU is
known to be several times slower than native execution.
…On Sat, Oct 29, 2022, 22:13 Eric Dallo ***@***.***> wrote:
Sorry for not clarrifying, I used this action for some time on clojure-lsp
<https://github.com/clojure-lsp/clojure-lsp/> to compile it to graalvm on
aarch64, and the action take ~1h-15m while other builds take 10-15mins
https://github.com/clojure-lsp/clojure-lsp/actions/runs/3191211682/jobs/5207278718
—
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABYUQVOZB5EZ3A2BPWXFKTWFWANTANCNFSM5NV6IBGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I see, so it's a QEMU limitation, maybe we should mention it somewhere on the readme? |
I'm compiling something heavy on this action, I'd like to use all memory/cpu from github runner, how to achieve that?
The text was updated successfully, but these errors were encountered: