4 ms·
I do not understand this. You have better "desktop CPUs" and want to be 4x faster then github actions? Most of CI time is spend on downloading stuff or moving f
by typingmonkey 5y ago
I do not understand this. You have better "desktop CPUs" and want to be 4x faster then github actions?
Most of CI time is spend on downloading stuff or moving files, how can this ever be 4x faster with just better CPUs?
> On average it reduces the CI run time by 50% (we forked and tested on ~100 public repos)
So in reality is is just 2x faster on non-optimized public repos?
- thinkafterbef 5y agoThe 4x faster came from our first attempt - writing a complete CI (UI + infrastructure). The performance improvements mainly came from good hardware, a more aggressive cache on dependencies, and a docker layer cache. The 2x improvements is referring to our latest product BuildJet for GitHub Actions, which is a plug-in runner for your existing GitHub Action pipeline. I hope that clarified it.
- typingmonkey 5y agoYes this clarifies it, thank you.