On 3/2/2011 4:07 PM, Rex Gozar wrote:
Optimization is about getting rid of bottlenecks in the code. Does
this code snippet really represent a significant percentage of the
total processing time? Really, what percent? If you can't quantify
it, don't change it.
rex
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
+1.
* /"We should forget about small efficiencies, say about 97% of the
time: premature optimization is the root of all evil. Yet we
should not pass up our opportunities in that critical 3%.A good
programmer will not be lulled into complacency by such reasoning,
he will be wise to look carefully at the critical code; but only
after that code has been identified"/^[5]
<http://en.wikipedia.org/wiki/Program_optimization#cite_note-4> -
Donald Knuth <http://en.wikipedia.org/wiki/Donald_Knuth>
* /"Bottlenecks occur in surprising places, so don't try to second
guess and put in a speed hack until you have proven that's where
the bottleneck is."/ - Rob Pike
<http://en.wikipedia.org/wiki/Rob_Pike>
* /"The First Rule of Program Optimization: Don't do it. The Second
Rule of Program Optimization (for experts only!): Don't do it
yet."/ - Michael A. Jackson
<http://en.wikipedia.org/wiki/Michael_A._Jackson>
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
