Why and When should you do a Profiling on Your Application?

There was a time that a bug was assigned to me saying that my module was slow as hell. I did profile my module (Delphi Native Win32 DLL Module) but didn’t find anything unusual. I had to profile the entire application (C# .NET), and was surprised to see the following:

refactoring-this-shit

Why should you do a Profiling on Your Application?

It is slow, but it does not mean it is because of what you’ve thought. Don’t make a judgement before it is properly tested and profiled.

When should you do a Profiling on Your Application?

Pre-optimisation is the evil of everything. Don’t waste your time on profiling unless there is indeed a performance bottleneck. If you attempt to optimise the module that is currently working pretty-well, you might end up:

• Wasting your time and achieving nothing
• Breaking the code especially if there are no enough/proper unit tests covered.
• If the module is not performance critical, the overall performance speed-up may be trivial due to the Ahmdal’s Law

You might also consider using the static analyser to hunt the potential problems in your code.

–EOF (The Ultimate Computing & Technology Blog) —