Re: [gentoo-dev] Some suggestions

[Luke-Jr]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I did a bogomips test a while ago and it wasn't anywhere close, IIRC.
There could have been some other factor I missed though, as I was basing my 
test on time an emerge took on my system and other one I don't have root 
on... (via the gest script)
For all I know, another emerge was going on concurrently or the task was 
suspended at one point.

On Sunday 07 September 2003 12:10 am, Steven Elling wrote:
> 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@g.o mailing list

- -- 
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/WoB0Zl/BHdU+lYMRAn/5AKCQeVExUv2nInxCgtuyLcOEkSoDQwCcCLtD
4quU+ILFri7aKRLfrdIiDRg=
=Cbd5
-----END PGP SIGNATURE-----


--
gentoo-dev@g.o mailing list