Confluence Docs 3.3 : Troubleshooting Slow Performance Using Page Request Profiling
This page last changed on Mar 10, 2010 by jlargman.
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: Enabling Page-Request Profiling
From 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()) ... Start Confluence with Profiling EnabledThere may be some situations where you may wish to have Confluence profiling enabled during startup. This may be useful if you restart often and may forget to enable profiling for Support/Trouble-shooting purposes. Edit the file CONFLUENCE_HOME\confluence\WEB-INF\web.xml. You should see a stanza similar to the one below. Set the parameter value for autostart to true: <filter> <filter-name>profiling</filter-name> <filter-class>com.atlassian.core.filters.ProfilingAndErrorFilter</filter-class> <init-param> <!-- specify the which HTTP parameter to use to turn the filter on or off --> <!-- if not specified - defaults to "profile.filter" --> <param-name>activate.param</param-name> <param-value>profile</param-value> </init-param> <init-param> <!-- specify the whether to start the filter automatically --> <!-- if not specified - defaults to "true" --> <param-name>autostart</param-name> <param-value>true</param-value> </init-param> </filter> Remember to turn it back to false or your logs will grow very large. RELATED TOPICSRequesting Performance Support |
![]() |
Document generated by Confluence on Jul 09, 2010 01:09 |