Thanks for the numbers Jo. The current hello-world setup with drone.io was done on cheap SSD based VPS. That said, with some "optimizations" (or hacks if you want) I think it should be possible to have less powerful servers but more of them to do what is needed.
For example, if one makes pull request for package A. Then for every target only the core system with package A and it's dependencies should be built. That said, if pull request is valid it will result with a successful build. We should avoid situations where somebody makes a patch for package A and if fails to build because package Z unrelated to package A is broken. Luka On Tue, May 24, 2016 at 10:35:42PM +0200, Jo-Philipp Wich wrote: > Hi, > > here's a few numbers we gathered with our buildbot setup: > > We currently need roughly 35GB per target when building OpenWrt plus the > entire package world and currently there are roughly ~70 > target/subtarget combinations in the OpenWrt tree. > > If fast build tests are desired then the only way to do so is by > implementing incremental building which only works if there's enough > space to retain all build trees at once which means there need to be > about 2.5TB of storage available. > > For only building all base systems without package feeds the entire > required space is around 800GB. > > A base system build currently requires 1 hour and 15 minutes on a > machine having a Xeon E3-1246 v3 4 core / 8 thread CPU with prepopulated > dl/, ccache and make -j8. > > A build of all packages from all feeds takes around 70 minutes on a Xeon > E5-2630 v3 8 core / 16 thread machine with 12GB ram and make -j16. > > HTH, > Jo > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
