On Sun, Feb 18, 2018 at 07:54:28PM +0100, Igor Gnatenko wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Sun, 2018-02-18 at 18:38 +0000, Richard W.M. Jones wrote: > > On Sun, Feb 18, 2018 at 06:09:40PM +0100, Igor Gnatenko wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA256 > > > > > > Over this weekend I've performed scratch-mass-rebuild without having > > > gcc and gcc-c++ in buildroot of all Fedora packages, > > > > Do you mind me asking how long that took (weekend = 2 days?!) and what > > sort of computing resources you used? I'd like to compare it to the > > rebuild we're doing for riscv64. > > Yes, 2 days (7 hours less if I would notice out of disk space). It was that > fast because 5k builds (1/4 of all packages) failed pretty quickly with missing > gcc 😉 > > * 4x Intel(R) Xeon(R) CPU E7-8860 v4 @ 2.20GHz > * 256 GiB RAM > > Actually not all resources have been used, I had 10 koji builders on this > server with 12 CPUs and 16G memory each. Interesting stuff, I didn't think it would be so fast even given the dependency failures. On: * 16 x Intel(R) Xeon(R) CPU E5-2609 v4 @ 1.70GHz * 64 GB RAM it's probably going to take something like 5 or 6 days to mass rebuild for Fedora/RISC-V (using qemu-system-riscv64). This is not very comparable however because: (a) we're not recompiling any noarch packages, we're just copying those in from Koji, and (b) probably only 20% of the archful packages can be successfully recompiled at this time. Status if interested: https://fedorapeople.org/groups/risc-v/autobuild-status.html (it updates at the bottom of the page). Thanks, Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
