| View previous topic :: View next topic |
| Author |
Message |
error32
n00b
Joined: 23 May 2007
Posts: 6
|
 Posted: Mon Jun 11, 2007 10:36 am Post subject: emerge time prediction system |
 |
|
After searching around I could not find anything that matches my idea for predicting portage emerge time so I hope I'm not reposting an re-invention of the wheel.
In the past I tried out working through the Linux from scratch book. In that book they refer to the build time for a certain package in a unit called SBU.
So I thought, why not implement something like that in portage as following:
- computer compiles a specifically developed test package (called buildtimetester or something like that)
- the time needed for this package to compile is recorded and used to know how long 1 'SBU' would take on the machine
- for each package there should be a time in 'SBU' in the ebuild
- with that time known it should be possible to predict how long a package should take to emerge
Now probably this has already come up before, but as I wrote before I could not find it so I thought I'd share my thoughts... |
|
| Back to top |
|
 |
erikm
l33t
Joined: 08 Feb 2005
Posts: 634
|
| Posted: Mon Jun 11, 2007 10:41 am Post subject: |
|
|
It already exists. Emerge 'genlop'. It will predict the required time for install based on previous builds, as well as record other data.
| Code: | ~$ genlop -i openoffice
* app-office/openoffice
Total builds: 3
Global build time: 10 hours, 27 minutes and 51 seconds.
Average merge time: 3 hours, 29 minutes and 17 seconds.
Info about currently installed ebuild:
* app-office/openoffice-2.2.0
Install date: Thu Jun 7 20:44:51 2007
USE="cups firefox gtk pam -binfilter -branding -cairo -dbus -debug -eds -gnome -gstreamer -kde -ldap -mono -sound -odk -seamonkey -webdav"
CFLAGS="-O2 -pipe -fomit-frame-pointer" |
|
|
| Back to top |
|
|
error32
n00b
Joined: 23 May 2007
Posts: 6
|
| Posted: Mon Jun 11, 2007 10:42 am Post subject: |
|
|
| awsome, thanks a lot |
|
| Back to top |
|
|
frnk
n00b
Joined: 02 Feb 2012
Posts: 14
|
| Posted: Wed Jun 23, 2021 10:05 am Post subject: |
|
|
Dude... Just did a "emerge -av genlop" which gave me a 42 packages list of stuff ... the whole perl universe. 
Is there something like genlop made with python? I don´t want to clutter my nice and small system. |
|
| Back to top |
|
|
timeBandit
Bodhisattva
Joined: 31 Dec 2004
Posts: 2719
Location: here, there or in transit
|
| Posted: Wed Jun 23, 2021 1:21 pm Post subject: |
|
|
| erikm wrote: | | It already exists. Emerge 'genlop'. It will predict the required time for install based on previous builds, as well as record other data. |
Genlop is handy but is not the answer to the OP's question because as its name implies (Gentoo Log Parser), its time estimates are derived from emerge logs. That means it cannot estimate at all a package that hasn't been built on the target machine at least once previously. Also, any significant change to the build environment (e.g., adding distcc, adding memory, installing an SSD, tuning make.conf, etc.) throws off the accuracy of genlop's estimates, perhaps by quite a lot.
Estimates based on the standard build unit (SBU) concept would not have those shortcomings. Doing it right, though--to the point of including build-time estimates in the output of emerge -p|-a, and/or at the start of each package merge--is probably an EAPI change, which is sort of a big deal.
_________________
Plants are pithy, brooks tend to babble--I'm content to lie between them.
Super-short f.g.o checklist: Search first, strip comments, mark solved, help others. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
