From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11036 invoked by uid 1002); 25 Jul 2003 18:55:07 -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 12563 invoked from network); 25 Jul 2003 18:55:06 -0000 From: Chris Gianelloni To: gentoo-dev@gentoo.org In-Reply-To: <1059160421.2178.5.camel@sergey.swdevelopers.net> References: <200307251956.27193.ripat@xs4all.nl> <1059160421.2178.5.camel@sergey.swdevelopers.net> Content-Type: text/plain; charset=koi8-r Message-Id: <1059159296.4089.6.camel@vertigo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 25 Jul 2003 14:54:56 -0400 Content-Transfer-Encoding: quoted-printable Subject: Re: [gentoo-dev] compile time statistics X-Archives-Salt: 28c4f7c1-f90c-42f2-8843-7e905eda9aef X-Archives-Hash: 06a16115019cbe14e7963167acdd05a0 Creating your own unit of measure is probably the best way to go about it. There are simply so many variables that can affect the build time of an ebuild... CPU type/speed, number of CPUs, USE flags, CFLAGS. We would definitely have to base the default USE/CFLAGS of the GRP. On Fri, 2003-07-25 at 15:13, Svyatogor wrote: > I was actually thinking of making this proposal :) > Just a small comment. In LFS you can find estimate compile time in SBU > (Standart Bash Units - time required to compile bash). It would be nice > if we could include this kind of information into ebuild. Any ideas on > whether that would be possible to do? >=20 > =F7 ?? 25.07.2003, =D7 20:56, Rutger Lubbers =D0=C9=DB=C5=D4: > > People, > >=20 > > This mail is about a question. The question is "how long does package= x.y.z=20 > > take to compile on my machine?" Now my idea is, we have the emerge.lo= g file=20 > > and can obtain some data from it, so we might "predict" that compile = time for=20 > > that user. > >=20 > > To get a fairly good prediction I need data. To get data I perhaps ne= ed a=20 > > prediction. Which needs data. So at the moment I don't know what to d= o.=20 > >=20 > > One part I have finished right now, I can get the compile times from = the=20 > > emerge.log and submit it to a central database (see http://ripat.xs4a= ll.nl). > > Some "basic" querying I can do too. > >=20 > > My questions to you is: > > - would this be a nice feature to have? > > - would you be willing to provide me with compile time statistics? > > - do you have any hints / ideas what I can do to get this from a no d= ataless=20 > > project to a data having project? > >=20 > > Thanks, > >=20 > >=20 > > Rutger Lubbers > >=20 > >=20 > > -- > > gentoo-dev@gentoo.org mailing list --=20 Chris Gianelloni Developer, Gentoo Linux -- gentoo-dev@gentoo.org mailing list