Performance Issues in .Net Application

According to me sometimes we found some performance issues in .Net application which are following:
Locking and Synchronization
Unnecessary logging
Dependencies of code
Major database issues
Major infrastructure issues
So anyone can found other issues, let me know if so.

Those aren’t performance issues strictly because it’s a .net application.

Those are common bottlenecks, sometimes necessary (locking and synchro for example), some are battle scars (extra logging to resolve issues or to cover themselves for other issues) and some are just poor design choices and/or examples of needing to factor code/databases which haven’t been done due to time/money/laziness.

Thanks for reply Dave

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.