expressappframework-402150-debugging-testing-and-error-handling-performance-application-performance.md
This article explains how to profile code performance and avoid common performance issues.
If SQL profilers did not reveal any issues and data model tune-ups did not help, you can profile your application code (both speed and memory consumption). This is an advanced task: before you begin, review basic concepts in trusted resources, such as Microsoft documentation.
Method execution time and call count:
Memory consumption:
The following blog post describes how to use different tools and techniques together: The Compromise Between Development Time and Performance in Data-Driven ASP.NET MVC.
Note
The list of commercial profiling tools above is incomplete and is provided for informational purposes only. DevExpress is neither responsible for nor does it endorse any content offered by third-parties.
After you obtain diagnostic information, check the following common causes for performance issues. We recommend that you follow all the advice from this list in your application.
The application or an individual View is loaded slowly for the first time (typically with scheduler, dashboards or reports), but subsequent loads are faster.
The application always starts slowly.
References to non-existent assemblies or types in the AssemblyName and TypeName columns of the service XPObjectType table. This may happen if you use XPO for data access and have been developing/upgrading your app for a long time.
A View is painted slowly, and the application freezes when it is necessary to redraw this View.
The application creates many entries in the Output window while debugging or in production, and this slows down its performance.
A Web application works very slowly while debugging.
The Excessive Conditional Appearance rule updates due to control value changes.