[All Adaptavist Apps]

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

(info) This page is specific to Theme Builder 1.x but most of what's described here is applicable to later versions.

Theme Builder enables Confluence to be used as a Content Management System (CMS) - as a result, people are likely to include more media elements (images, etc.) and macros Macros in pages to make them more aesthetically pleasing and functional.

...

Users of Builder 2.0 should should review our Caching Overview.

Solution

The easiest solution is to upgrade to Confluence 2.2 or above and Theme Builder 2.x or above.

...

Users of Builder 2.0 should review our Menu Performance Tuning tutorial.

Workaround

Prior to a patch being available for Confluence, you can upgrade to Builder 1.6 or above which has an option to load the menu as quickly as possible.

...

Users of Builder 2.0 should review our Menu Performance Tuning tutorial.

Solution

The most obvious solution is to limit the size of the menus generated with macros. Smaller menus will be faster.

...

If you use macros within footers, extra processing will usually be required on the server whilst those macros go off and get additional information from the database, etc.

Solution

Use the cache macro to cache your footer.

Expand
Example - Caching the footer
Example - Caching the footer

Let's say your footer contained this:

No Format
{some-macro} {another-macro}
some wiki text or whatever

You can cache that footer, on a page by page basis, as follows:

No Format
{cache:refresh=1d}{some-macro} {another-macro}
some wiki text or whatever{cache}

In the example shown above, the footer will be cached for 1 day for each page.

...