From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7308 invoked by uid 1002); 7 Sep 2003 00:10:41 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 25741 invoked from network); 7 Sep 2003 00:10:41 -0000 From: Steven Elling To: gentoo-dev@gentoo.org Date: Sat, 6 Sep 2003 19:10:34 -0500 User-Agent: KMail/1.5.2 References: <459A860E-E0B5-11D7-ABF7-00306580AC5C@wisc.edu> In-Reply-To: <459A860E-E0B5-11D7-ABF7-00306580AC5C@wisc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309061910.34278.ellings@kcnet.com> Subject: Re: [gentoo-dev] Some suggestions X-Archives-Salt: 89a77f32-a2aa-4974-98fe-6265b42d648a X-Archives-Hash: 36c8be7b170868fb81a5560a2ef69806 On Saturday 06 September 2003 16:58, Brian Harring wrote: > Eh, wouldn't hold or be particularly accurate, mainly since I/O, proc > speed, and available memory (let alone if another job is running in the > background and hogging cycles) are too many variables (imo) to try and > factor out. > Someone a while back had a setup such that they parsed the makefile, > figuring out the number of actions (gcc calls, ar calls, mv/cp/install > commands), and tracked progress that way. Strikes me as the better > way, although some packages weren't able to be parsed correctly > resulting in a compilation progress reading at rather off values like > 1100% and counting... > ~bdh What about using a bogomips seconds factor to determine a `close estimate' of how long a package will take to compile? Here is something I posted to another mailing list: ==================== Subject: OpenOffice build on Gentoo / Determining how long it will take? Date: 2003-05-28 14:07 I timed the build of OpenOffice on Gentoo yesturday using the following command: time emerge -Du openoffice The build of version OpenOffice 1.0.3-r1 completed today and time spit out the following: real 844m6.053s user 704m12.660s sys 31m30.340s Overall, the build of OpenOffice on my system (Athlon 900 MHz) took 14 hours 4 minutes and 6.053 seconds. I would think a good way to determine how long a build will take on your system is to divide a bogomips seconds factor by the bogomips from /proc/cpuinfo ( x / bogomips = time ) then throw in a fudge factor of 10%. Any thoughts anyone? The bogomips seconds factor could be determined by compiling OpenOffice on several systems using the time command to record the amount of time it takes, calculating the bogomips seconds factor for each system using the formula "time * bogomips = x" and then averaging the numbers. On my system, the bogomips are 1782.57 so the bogomips seconds factor for OpenOffice would be 50646.053 seconds * 1782.57 bogomips = 90280134.6962 bogomips seconds. Using the bogomips seconds factor from above, my laptop should take 90280134.6962 bogomips seconds / 730.72 bogomips = 123549.5602 seconds (34 hours 19 minutes and 9.5602 seconds) +- 10%. I'll find out how long it actually takes sometime in the next week because I'm currently updating Gentoo on it. ==================== -- gentoo-dev@gentoo.org mailing list