Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84; site hplabsc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!hplabsc!bs
From: bs@hplabsc.UUCP (Bob Shaw)
Newsgroups: net.unix,net.lang.c
Subject: How do I make it better?
Message-ID: <174@hplabsc.UUCP>
Date: Thu, 3-Apr-86 22:54:20 EST
Article-I.D.: hplabsc.174
Posted: Thu Apr  3 22:54:20 1986
Date-Received: Sat, 5-Apr-86 10:43:12 EST
Distribution: net
Organization: Hewlett Packard Labs, Palo Alto CA
Lines: 24
Xref: watmath net.unix:7538 net.lang.c:8398

*** REPLACE THIS LINE WITH YOUR MESSAGE ***


I'm trying to find out about tools and techniques people use
to "improve" their code.  By "improve" I don't mean debug,
but rather make functioning code reduce its execution time, size 
and utilization of other resources.  

Everyone seems to know about (the UNIX tools) prof, gprof, 
vmstat and iostat.  I was brought up on the "put it in a loop and
use a stopwatch" technique.  Are these really all that is necessary?
What I'm looking for are other tools (commercial or research) 
and techniques that are effective in giving useful feedback about 
how well a user's program is performing.  Can anyone help?  What kind 
of feedback do YOU need to tune your code to a machine?

If you don't want to clog up the net, please feel free to
respond directly.  I'll summarize if there's sufficient interest.

                                 Thanks,
                                 Bob Shaw, HP Labs

                                 CSNET: ...!ucbvax!hplabs!shaw
                                 ARPA:  shaw@hplabs.ARPA