Tips & Tricks
How to Write High-Performance C# Code
Writing code that runs quickly is sometimes at odds with writing code quickly. C.A.R. Hoare, computer science luminary and discoverer of the QuickSort algorithm, famously proclaimed, 'Premature optimization is the root of all evil.' The extreme programming design principle of 'You Aren't Gonna Need It' (YAGNI) argues against implementing any features, including performance optimizations, until they're needed.
Reader Feedback: Page 1 of 1
#8 |
You can simplify your micro benchmarks code by using the System.Diagnostics.Stopwatch class
|
#7 |
Duty Editor commented on 28 Dec 2007
Thank you Daniel, we are contacting the plagiarist and will insist the article immediately be pulled down from his site.
Duty Editor
SYS-CON Media
|
#6 |
Daniel commented on 28 Dec 2007
You have been plagarized on http://www.thescripts.com/forum/showthread.php?p=3001766#post3001766
|
#5 |
Goku commented on 21 Sep 2007
well written article. very useful
|
#4 |
Sam commented on 9 Feb 2006
I could not get the sample code downloaded. Please make it accesible again.
|
#3 |
Enrique commented on 5 Aug 2005
Hi
I'm not agree with you affirmation about Collections, what happen with software architects that are building its Data Access Layers around Collections?. Can you be more specific about this affirmation?
There are many articles on the web Custom Objects vs. DataSet Objects giving a partial victory to Collections based Custom Objects (including performance)
Thanks
|
#2 |
Mikalai commented on 18 Dec 2004
One better use threads. It forces you to THINK using threads, be comfortable with them. The is a HUMAN bottleneck, which is we think in single thread only. And if you write many threads, you excercise what is missing, becaming more valuable programmer. By the way, soon will have multicore processors. Unfortunately, there is tooo much of single thread programs, that will NOT take advantage of great new technologies!
|
#1 |
Mikalai commented on 18 Dec 2004
As an example of a place where early optimization is OK you take task where optimization is on the Priority List, which means you should take care of it IF you do eXtreme programming. Article is fine, its just this preambule is false. XP is about doing what you HAVE to do. Like many other agile techniques.
|