Fri Jun 27 10:01:01 CEST 2014
Build times
Just for fun, over about 8500 packages built, the slowest three:
These are also the only packages above 1h build time.
Average seems to be near 5 minutes (hard to filter out all the binpkg merges, which are silly-fast)
Edit: New highscore!
Fri Jun 13 19:40:13 2014 >>> dev-python/pypy-2.2.1 merge time: 2 hours, 7 minutes and 23 seconds. Fri Jun 20 09:58:38 2014 >>> app-office/libreoffice-4.2.4.2 merge time: 1 hour, 37 minutes and 22 seconds. Fri Jun 27 12:52:19 2014 >>> sci-libs/openfoam-2.3.0 merge time: 1 hour, 5 minutes and 8 seconds.(Quadcore AMD64, 3.4Ghz, 8GB RAM)
These are also the only packages above 1h build time.
Average seems to be near 5 minutes (hard to filter out all the binpkg merges, which are silly-fast)
Edit: New highscore!
Sun Jun 29 20:36:09 2014 >>> sci-mathematics/nusmv-2.5.4 merge time: 2 hours, 58 minutes.
Wed Jun 25 08:27:30 CEST 2014
Building Everything
Preparation:
Space usage:
~2.5G logfiles
~35G distfiles
~20G binary packages
~100G temp space (/var/tmp has lots of cruft unless FEATURES="fail-clean")
Triage of these logfiles yields about 1% build failures, on average.
It's not hard to do, just tedious!
make.conf additions:
- Take recent stage3 and unpack to a temporary location
- Set up things: make.conf, resolv.conf, keywords, ...
- Update @system, check gcc version etc.
- Clone this snapshot to 4 locations (4 because of CPU cores)
- bindmount /usr/portage and friends
for i in $( qsearch -NC --all | sort -R ); do if $( emerge --nodeps -pk $i > /dev/null ) ; then emerge --depclean; echo $i; emerge -uNDk1 $i; fi; doneWait 4-5 days, get >10k binary packages, lots of logfiles.
Space usage:
~2.5G logfiles
~35G distfiles
~20G binary packages
~100G temp space (/var/tmp has lots of cruft unless FEATURES="fail-clean")
Triage of these logfiles yields about 1% build failures, on average.
It's not hard to do, just tedious!
make.conf additions:
FEATURES="buildpkg split-log -news" PORT_LOGDIR="/var/log/portage/" MAKEOPTS="-j4" EMERGE_DEFAULT_OPTS="--jobs 4" CLEAN_DELAY="0" EMERGE_WARNING_DELAY="0" ACCEPT_PROPERTIES="* -interactive"
Tue Jun 17 09:13:34 CEST 2014
EAPI statistics, again
Start: Thu Jan 16 08:18:45 UTC 2014 End: Mon Jun 16 00:00:01 UTC 2014 EAPI 0: 5966 ebuilds (15.78 percent) -> 5477 ebuilds (14.40 percent) EAPI 1: 370 ebuilds (0.98 percent) -> 215 ebuilds ( 0.57 percent) EAPI 2: 3335 ebuilds (8.82 percent) -> 2938 ebuilds ( 7.72 percent) EAPI 3: 3005 ebuilds (7.95 percent) -> 2585 ebuilds ( 6.79 percent) EAPI 4: 12385 ebuilds (32.76 percent) -> 10375 ebuilds (27.27 percent) EAPI 5: 12742 ebuilds (33.71 percent) -> 16455 ebuilds (43.25 percent) Total 37803 -> 38045 EAPI 0 change: -8.2% EAPI 1 change: -58.1% EAPI 2 change: -11.9% EAPI 3 change: -14.0% EAPI 4 change: -16.2% EAPI 5 change: +29.1%So over the last 5 months we had about 2% increase in the total amount of ebuilds. The only growing class is EAPI5, which is quite excellent.
EAPI 0 is the slowest decreasing, as long as there's no coordinated effort to get rid of it it'll be there forever. EAPI1 is now very close to extinction.
EAPI 2,3 and 4 are slowly shrinking away, but at this rate it'll still take years.