Identifying Slow Performing Macros
Page Profiling gives good detail on what operations are slow in a page load. In addition, you can add debug level logging:
Version 3.1 and Later
Set the package name
com.atlassian.renderer.v2.components.MacroRendererComponent to DEBUG in Administration >> Logging and Profiling.
Prior to version 3.1
Download WikiMarkupParser.class, available from the attachments to this page. This will result in logs like:
To add the class:
- Add this line to the file <confluence-install>/confluence/WEB-INF/classes/log4j.properties:
- Add the appropriate WikiMarkupParser.class to /confluence/WEB-INF/classes/com/atlassian/renderer/v2. You'll have to make the renderer and v2 folders.
In combination with page profiling, this should give good specifics on the amount of time various plugins take. You can also use this utility to Search Confluence for Uses of a Macro.
Experiment with the tips from the performance tuning page, or open an enhancement request about the specific macro. In some instances there is no resolution - you'll just be aware of the overhead of various macros.
Was this helpful?
Thanks for your feedback!