Re: 90/10 rule... source?

nkavv@skiathos.physics.auth.gr (Uncle Noah)
16 Jan 2004 22:55:55 -0500

          From comp.compilers
Related articles
RE: 90/10 rule... source? qjackson@shaw.ca (Quinn Tyler Jackson) (2004-01-09)
RE: 90/10 rule... source? qjackson@shaw.ca (Quinn Tyler Jackson) (2004-01-12)
Re: 90/10 rule... source? nkavv@skiathos.physics.auth.gr (2004-01-16)
Re: 90/10 rule... source? gah@ugcs.caltech.edu (glen herrmannsfeldt) (2004-01-17)
Re: 90/10 rule... source? derek@knosof.co.uk (Derek M Jones) (2004-01-17)
Re: 90/10 rule... source? jcownie@etnus.com (James Cownie) (2004-01-22)
Re: 90/10 rule... source? vidar@hokstad.name (2004-01-22)
Re: 90/10 rule... source? ieuk001@attglobal.net (2004-01-22)
Re: 90/10 rule... source? derek@knosof.co.uk (Derek M Jones) (2004-01-31)
| List of all articles for this month |
From: nkavv@skiathos.physics.auth.gr (Uncle Noah)
Newsgroups: comp.compilers
Date: 16 Jan 2004 22:55:55 -0500
Organization: http://groups.google.com
References: 04-01-046 04-01-049
Keywords: practice, optimize
Posted-Date: 16 Jan 2004 22:55:54 EST

Actually, the 90/10 rule (90% of the execution time in 10% of the
code) applies in some occasions.


In some application domains (image and video processing) there exist
algorithms with characteristics: loop-intensive constructs with deep
nests and large number of iterations. In addition to that, small
number of non-static branches.


To see if your application spends much time in specific portions of
the code you can perform some preliminary profiling with gprof. There
might exist some profiling tools that support per-instruction
profiling.


Uncle "The G.B. Man" Noah

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.