From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22078 invoked from network); 8 Sep 2004 12:04:02 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 8 Sep 2004 12:04:02 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1C51BC-0005JH-4U for arch-gentoo-dev@lists.gentoo.org; Wed, 08 Sep 2004 12:04:02 +0000 Received: (qmail 23841 invoked by uid 89); 8 Sep 2004 12:04:01 +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 28298 invoked from network); 8 Sep 2004 12:04:00 +0000 X-cybertrench.com-virus-scan: clean Date: Wed, 8 Sep 2004 14:03:58 +0200 From: Corvus Corax To: gentoo-dev@lists.gentoo.org Message-Id: <20040908140358.10e0be61@VikingPC.home> In-Reply-To: <200409081329.10457.pauldv@gentoo.org> References: <33333.10.0.0.51.1094638559.squirrel@10.0.0.51> <200409081329.10457.pauldv@gentoo.org> X-Mailer: Sylpheed version 0.9.11claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] Do we want optimal performance? X-Archives-Salt: 5621bf51-c2b3-4a35-aea2-e95e77cb6e68 X-Archives-Hash: 595c6ca15f78ea702d506e4e521a5b98 Am Wed, 8 Sep 2004 13:29:01 +0200 schrieb Paul de Vrieze : > ... > > To do this for programs, one would need to have a realistic suite of > "tests" that simulate the real world use of the application. Of course > that also allows -fprofile_arcs to be used. > > Paul > depending on the type of program - for easy command line converter tools, an easy "time" command would be sufficient (used that to determine potential (in code) optimizations for my motiontrack stuff) however for libraries like QT or gtk which affect on screen performace of gui programs - both run-time and load - this will get much harder. Maybe one could program a test-suite for each library that fires each function once and times them, along with a flag saved before startup to determine load time - but it would have to be done for every huge library. And finally the timing of interactive programs itself - well, usually most time goes while waiting for user input anyway, but there are timing critical tasks, too, imagine pattern searches or other big db operatins - or file load/save in openoffice, picture effects in gimp and such. those could maybe timed by doing them on a real huge data blog, where the single operation takes that long, that the user can measure it manually with a stopwatch. If the operation takes 40 seconds, and you can gain 3 seconds by optimisations, it is a blunt measurable improvement. However I dont like that idea, maybe one can time the operation by watching tmp files in background or something like this. Or the maintainer could go into the code and insert some debug lines to print timing information to stderr or such. But this would be way to much work for most maintainers and most software isnt it ? (Well I still could do it on my own software and tell the maintainer the result;) just some thoughts... regards Corvus -- gentoo-dev@gentoo.org mailing list