How to increase memory/cpu dedicated to container? about run-on-arch-action

[martin-g]

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: ***@***.***>

[uraimo]

Here :) https://github.com/uraimo/run-on-arch-action#architecture-emulation

[martin-g]

Why do you believe the Docker container started by the action uses less resources ?
Unless you specify some limits in your dockerRunArgs it must use all available resources.

[ericdallo]

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
https://github.com/clojure-lsp/clojure-lsp/actions/runs/3191211682/jobs/5207278718

[ericdallo]

I see, so it's a QEMU limitation, maybe we should mention it somewhere on the readme?