Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!ernie!pincus
From: pincus@ernie.BERKELEY.EDU (Jonathan Pincus)
Newsgroups: net.lang.prolog
Subject: profiling prolog programs?
Message-ID: <10751@ucbvax.ARPA>
Date: Sun, 20-Oct-85 23:52:26 EDT
Article-I.D.: ucbvax.10751
Posted: Sun Oct 20 23:52:26 1985
Date-Received: Tue, 22-Oct-85 04:56:40 EDT
Sender: usenet@ucbvax.ARPA
Reply-To: pincus@ernie.BERKELEY.EDU (Jonathan Pincus)
Organization: University of California, Berkeley
Lines: 16


Has anybody out there ever tried to profile a prolog program?  Specifically,
how do I find out how much time various procedures require?  Obvoiusly, I
want to do this in order to speed up the program in the important places
(for that matter, does the old chestnut about 10% of the code requiring 90%
of the execution time hold for prolog?).

My specific environment is Cprolog (version 1.2) on a VAX.  One thought
that has occurred to me is that timing information needs to be recorded
at the same time that "spy"ing information gets printed out, but I'm not
sure how to do that.  Any comments/advice/solutions will be gratefully
accepted, and if anything exciting turns up I'll post a summary . . . but
please DON'T tell me "Oh, that's just an efficiency question, you shouldn't
worry about that!"

jon 					pincus@ernie.berkeley.edu