3 ms·
Hi, quick question: > Runners are assigned to hardware that is ideal for build workloads with [...] high single-core performance In my kind of projects (C++,
by lionkor 3y ago
Hi, quick question:
> Runners are assigned to hardware that is ideal for build workloads with [...] high single-core performance
In my kind of projects (C++, Rust, C) the builds are highly parallelizable, so single core performance is generally not what you want, if you can instead get a lot of cores.
The main bottleneck to my own build pipelines on github was how painful it is to use containers, and how "helpful to idiots but not experts" a lot of the github actions docs are (microsofts style, I guess?).
Good luck though!
- suryao 3y agoWe do have high core options too (up to 16) but not crazy high like with GPUs. You'll probably still see good benefits. Could you elaborate on the pain points with using containers?
- lionkor 3y agoYes! everything changes when using containers, whereas in gitlab everything is based on containers to begin with
- xjia 3y agoWe support machines with large core counts in https://dime.run https://dime.run so check it out :)
- crohr 3y agoIf you need machines with high number of CPUs, you can check https://github.com/runs-on/action https://github.com/runs-on/action which allows you to select any EC2 instance type as ephemeral runner. Plus it’s the cheapest on the market, open source, and not a SaaS