Xref: utzoo comp.lang.c:27327 comp.lang.misc:4675
Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!hp4nl!kunivv1!ge
From: ge@kunivv1.sci.kun.nl (Ge' Weijers)
Newsgroups: comp.lang.c,comp.lang.misc
Subject: Re: A note for those not consumed by efficiency worries
Message-ID: <1241@kunivv1.sci.kun.nl>
Date: 28 Mar 90 15:39:08 GMT
References: <1990Mar21.061420.9862@athena.mit.edu> <1990Mar21.163413.10711@aqdata.uucp> <1990Mar22.072712.10902@diku.dk> <1084@targon.UUCP>
Organization: University of Nijmegen, The Netherlands.
Lines: 28

ruud@targon.UUCP (Ruud Harmsen) writes:

>In article <1990Mar22.072712.10902@diku.dk> jensting@skinfaxe.diku.dk (Jens Tingleff) writes:
>>
>>	MAKE THE THING WORK, THEN MAKE IT FAST.
>>
>True.  But only with one very important footnote:

>While making the thing just work, do consider performance, and know where and
>how you might want to optimise later.
>If in the design of a programme or system you totally disregard all
>performance issues, you might have to rebuild large parts from scratch,
>and/or make the whole thing totally incomprehensible when optimisizing.

>I've seen things like that happen, and I can tell you it's a tragic sight
>to watch.  A much better approach is to have the spots for optimization
>marked and planned, so it is easy to fulfill, will be really effective
>and does not violate the original design.

I have to second that. You have to look at the feasibility of what you are
doing. If your solution of a problem is O(e ** N) for large N, look for a
better solution.

You still need to do some rough calculations.
Ge' Weijers                                    Internet/UUCP: ge@cs.kun.nl
Faculty of Mathematics and Computer Science,   (uunet.uu.net!cs.kun.nl!ge)
University of Nijmegen, Toernooiveld 1         
6525 ED Nijmegen, the Netherlands              tel. +3180612483 (UTC-2)