When Should You Do Your Performance Tweaking ?

My approach to performance tweaking is simple... defer it as long as possible !  There are two main problems when worrying about performance, first until the system is completed, you cannot say for sure where the biggest and worst  bottlenecks are going to occur.  Second, that in order to be able to successfully do any performance tweaking, you must be able to measure that what you are changing actually improves performance.  If you're developing a real time life critical system then this doesn't apply to you, but I'm assuming this doesn't apply to most people. In all performance optimizations you need to test and verify the results.  Different techniques will improve and reduce quality in different languages and environments.  Just because your tweak worked in VB doesn't mean it will improve performance in C#.  The only way to prove this is to TEST!

Jon D Jones

Software Architect, Programmer and Technologist Jon Jones is founder and CEO of London-based tech firm Digital Prompt. He has been working in the field for nearly a decade, specializing in new technologies and technical solution research in the web business. A passionate blogger by heart , speaker & consultant from England.. always on the hunt for the next challenge

Back to top
var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-35662136-1']); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + 'stats.g.doubleclick.net/dc.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })();