Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!acw!guthery
From: guthery@acw.UUCP (Scott Guthery)
Newsgroups: comp.object
Subject: Performance & Functionality
Message-ID: <27.UUL1.3#913@acw.UUCP>
Date: 24 Oct 89 05:07:56 GMT
Organization: Austin Code Works
Lines: 21

Functionality first and performance at the end is wrong.  If you
care about performance then you should design it in not hack
it in.  Furthermore, you might avoid the situation where the
design you've implemented simply can't be whipped up to speed.
If all you want is as fast as possible, then by all means
profile and stomp on the hot spots.  But if you have a performance
bogey, then you'd better care quantitatively from the start.
Consider the situation where all the hot spots are gone, the
profile is flat, and it's still not fast enough.  How now, 
brown cow?
							Cheers, Scott

+*+*+*+*+*+*+*+*+*+*+*+*+ Austin Code Works +*+*+*+*+*+*+*+*+*+*+*+*+*+*+**+*+
NET Domain: guthery@uunet.uu.net           Post:  11100 Leafwood Lane
COM Domain: guthery@acw.com                       Austin, Texas 78750-3409 USA
US  Domain: guthery@acw.austin.tx.us       FAX:   +1 (512) 258-1342
Usenet:     {uunet}!acw!guthery            Voice: +1 (512) 258-0785
CompuServe: 70240,221                      TELEX:    446370 (austincodewrks)
Packet:     N5MDE @ KB5PM                  EasyLink: 62752994
Fidonet:    1:382/12                       Prodigy:  KSWS89A 
+*+*+*+*+*+*+*+*+*+*+*+*+* The Source of C +*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+