Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!uwvax!uwmacc!uwmcsd1!leah!itsgw!batcomputer!tedcrane
From: tedcrane@batcomputer.UUCP
Newsgroups: comp.os.vms
Subject: Re: VAX Performance and Coverage Analyzer
Message-ID: <1300@batcomputer.tn.cornell.edu>
Date: Mon, 8-Jun-87 14:42:49 EDT
Article-I.D.: batcompu.1300
Posted: Mon Jun  8 14:42:49 1987
Date-Received: Thu, 11-Jun-87 01:55:48 EDT
References: <870606055152.01g@lbl.arpa>
Reply-To: tedcrane@tcgould.tn.cornell.edu.UUCP (Ted Crane)
Distribution: world
Organization: Program of Computer Graphics, Cornell University
Lines: 16

We have PCA.  I've used it a bit.  There are a lot of commands, and
it may take a while to learn to use them all, BUT you can do the
most obvious kinds of inspection (like finding which line of code is
eating most of your CPU time) quite easily.

Several of our users have made use of PCA.  In each case, it has helped
them identify problem spots.  In some cases they were able to improve 
performance as a result.  Isolated code fragments were sped up up to maybe
six times (love that up up).

If tuning your program is within your time budget, and you can affort PCA,
we'd recommend it!

- ted crane, alias (tc)
tedcrane@squid.tn.cornell.edu                         BITNET: tedcrane@CRNLTHRY
{decvax!ucbvax}!squid.tn.cornell.edu!tedcrane               DECnet: GOPHER::THC