Confluence 2.9 : Troubleshooting Slow Performance Using Page Request Profiling
This page last changed on Aug 07, 2008 by smaddox.
This page tells you how to enable page-request profiling. With profiling turned on, you will see a record of the time it takes (in milliseconds) to complete each action made on any Confluence page. If Confluence is responding slowly, an internal timing trace of the slow page request can help to identify the cause of the delay. You will need access to the Confluence server to view a profile. In this page: Error formatting macro: toc: java.lang.NullPointerException
Enabling Page-Request ProfilingThere are two ways to turn on profiling for your Confluence instance:
Both methods are described below. Using a Page's URL to Enable/Disable Profiling
Using the Administration Console to Enable/Disable ProfilingFrom Confluence 2.7, you can use the 'Logging and Profiling' option to enable or disable profiling.
To enable page profiling,
To disable page profiling,
Profiling an Activity
Example of a ProfileBelow are the first few lines of a normal profile for accessing a page called Confluence Overview. [344ms] - /display/ds/Confluence+Overview [313ms] - SiteMesh: parsePage: http://localhost:8080/display/ds/Confluence+Overview [313ms] - XW Interceptor: Before defaultStack: /pages/viewpage.action (ViewPageAction.execute()) [0ms] - SpaceAwareInterceptor.intercept() [16ms] - PageAwareInterceptor.intercept() [0ms] - AOP: PageManager.getPage() [16ms] - AOP: PermissionManager.hasPermission() [0ms] - AOP: SpacePermissionManager.hasPermission() [16ms] - AOP: SpacePermissionManager.hasPermission() [0ms] - AOP: SpacePermissionManager.hasPermission() [0ms] - AOP: SpacePermissionManager.hasPermission() [281ms] - XW Interceptor: After defaultStack: /pages/viewpage.action (ViewPageAction.execute()) [281ms] - XW Interceptor: After validatingStack: /pages/viewpage.action (ViewPageAction.execute()) ... RELATED TOPICSRequesting Performance Support |
![]() |
Document generated by Confluence on Aug 07, 2008 19:05 |