From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16044 invoked by uid 1002); 5 Aug 2003 16:03:43 -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 14926 invoked from network); 5 Aug 2003 16:03:43 -0000 Message-ID: <3F2FD54F.1010505@gentoo.org> Date: Tue, 05 Aug 2003 12:03:27 -0400 From: Stewart Honsberger Organization: Gentoo Technologies User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030710 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chris Gianelloni Cc: =?ISO-8859-1?Q?H=E5vard_Wall?= , gentoo-dev@gentoo.org, werner.van.belle@vub.ac.be References: <200307251956.27193.ripat@xs4all.nl> <1059160421.2178.5.camel@sergey.swdevelopers.net> <200307252052.09728.werner.van.belle@vub.ac.be> <3F22506A.8050902@ifi.uio.no> <1059227442.24877.25.camel@vertigo> In-Reply-To: <1059227442.24877.25.camel@vertigo> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] compile time statistics X-Archives-Salt: 3cad405f-c381-4ef3-a71c-95869a81298b X-Archives-Hash: e667a31fe23399bbbaa73e0055401b65 Chris Gianelloni wrote: > To be anywhere near the correct answer you would need to know: > - CPU type > - CPU speed > - Number of CPUs > - MAKEOPTS > - USE flags > - Some of the CFLAGS, particularly -march and -O I'm seeing a matrix of information stored in a database. With Gentoo being so dynamic, we could have a stats component check each of the variables and take a sampling of similar system configurations in the database. What I forsee (correct me if this has already been discussed; I'm only getting around to reading this list seriously now after some time working long hours) goes along the lines of this; Integrate stats into Portage somehow so that it becomes transparent. Perhaps even a module that can be merged separately of Portage. Otherwise, were it merged directly into Portage itself, we have a make.conf flag that enables stats. We inform the user, naturally, what stats will be taken, how they will be processed, and where they will be stored. We inform users that stats are a two-way street. Much like the GPL, you can't take without giving. If you want a figure on how long each item should take to compile, you have to permit the sending of how long it TOOK to compile on your system to add to the numbers in the database. As with any statistical reporting, I also see a system whereby numbers that are really off-base with the rest of the numbers in the same category be disgarded. If my Athlon XP 1800+ system reports that it took >48 or <2 hours to compile OpenOffice, for example, that number would be thrown away as somehow invalid. In this matrix we could include a variable for 'ccache', which would give us a good baseline of how well ccache helps compile times. For example, my system some time ago would be reported / queried using; CPU = AMD Athlon 1800+ RAM = 512MB DDR CC = gcc (GCC) 3.2.2 CFLAGS = CFLAGS="-march=athlon-xp -Os -pipe -mfpmath=sse,387" CCACHE = yes Perhaps the logic used in "emerge -v {package}" could be incorporated to find systems with similar USE flags. Obviously nomozillamail et al. will decrease Mozilla's compile time. (Depositing $0.02 on table) -- Stewart Honsberger Gentoo Developer http://www.snerk.org/ -- gentoo-dev@gentoo.org mailing list