Page History

...

I enabled Confluence page profiling as decribed here: http://confluence.atlassian.com/display/DOC/Troubleshooting+Slow+Performance+Using+Page+Request+Profiling^{Image Removed}

In general I notice that non-theme builder spaces are relatively fast to load (~2 seconds) whereas theme builder spaces are ~5-6 seconds (similar to the other thread).

Here are some of the details of a page load on our site for a page with a layout where the menu panel is disabled (does that make a difference? I'm trying to isolate performance bottlenecks...):unmigrated-wiki-markup

2009-02-07 12:24:02,970 DEBUG \ [http-443-1\] \ [atlassian.util.profiling.UtilTimerStack\] log \ [*486{*}ms\] - /display/caGrid13/Upgrade+caGrid+1.2+Grid+to+caGrid+1.3

Wiki Markup  \  [422ms\] - SiteMesh: parsePage: https://wiki.cagrid.org/display/caGrid13/Upgrade+caGrid+1.2+Grid+to+caGrid+1.3unmigrated-wiki-markup

\[56ms\] - SiteMesh: applyDecorator: main (templates/builder/theme/main.vmd)

....

Wiki Markup2009-02-07 12:24:04,987 DEBUG \ [http-443-9\] \ [atlassian.util.profiling.UtilTimerStack\] log \ [*177{*}ms\] - /plugins/builder/layout-resources.actionunmigrated-wiki-markup

\[37ms\] - SiteMesh: parsePage: https://wiki.cagrid.org/plugins/builder/layout-resources.actionunmigrated-wiki-markup

2009-02-07 12:24:06,188 DEBUG \ [http-443-2\] \ [atlassian.util.profiling.UtilTimerStack\] log \ [*1112{*}ms\] - /plugins/builder/layout-resources.actionunmigrated-wiki-markup

\[*574{*}ms\] - SiteMesh: parsePage: https://wiki.cagrid.org/plugins/builder/layout-resources.action

Wiki Markup\[*571{*}ms\] - XW Interceptor: Before defaultStack: /plugins/builder/layout-resources.action (LayoutResourcesAction.execute())

The profiling log doesn't seem to indicate within a particular action what is taking so long (e.g., the layout-resources.action takes 1112 ms total, and only 574ms of that is spent in the SiteMesh log line). Is there any additional information I can gather from theme builder (e.g., enable theme builder logs?) to get more detail?

...