Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!jade!ucbvax!ucsfcgl!cca.ucsf.edu!ccb.ucsf.edu!dick From: dick@ccb.ucsf.edu (Dick Karpinski) Newsgroups: comp.lang.modula2 Subject: Re: Converting from Turbo to Modula. Message-ID: <1066@ucsfcca.ucsf.edu> Date: Wed, 4-Nov-87 15:34:30 EST Article-I.D.: ucsfcca.1066 Posted: Wed Nov 4 15:34:30 1987 Date-Received: Sat, 7-Nov-87 16:28:35 EST References: <8711031748.AA10838@gpu.utcs.toronto.edu> Sender: root@cca.ucsf.edu Reply-To: dick@ucsfccb.UUCP (Dick Karpinski) Organization: UCSF Computer Center Lines: 25 Summary: To speed up: measure, think, alter, loop. In article <8711031748.AA10838@gpu.utcs.toronto.edu> Info-Modula2 Distribution List writes: > >I don't think the >slowness of the program has anything to do with the use of the >automatic conversion .... I have always found at least 20%, usually a factor of 2, and often a factor of 10 available in the speed of execution while working at the source level. The approach I use is to profile the working program (about 1 day, usually) and analyze the results carefully. These first results can be astonishing or mundane. Then I look for the parts that have high cost and find ways to avoid them or to greatly reduce the cost. Usually a single day of recoding can accomplish most of the readily available speedup. The key thing is to SEE where the time goes. But most folks really don't care to find out since they secretly believe that they will look silly when their program runs faster with so little work. Dick Dick Karpinski Manager of Minicomputer Services, UCSF Computer Center UUCP: ...!ucbvax!ucsfcgl!cca.ucsf!dick (415) 476-4529 (11-7) BITNET: dick@ucsfcca or dick@ucsfvm Compuserve: 70215,1277 USPS: U-76 UCSF, San Francisco, CA 94143-0704 Telemail: RKarpinski Domain: dick@cca.ucsf.edu Home (415) 658-6803 Ans 658-3797