Page Comparison

...

Render is the Confluence process that takes page markup and converts it into html that is sent to the browser. In simple terms, the time taken to display the page in the browser is determined by:

• Server processing - Confluence server processing that converts page markup into html
• Download time - to transfer the html and all referenced images, scripts, and related information to the browser
• Browser - rendering time

Constraints

Cache for Confluence is constrained by:

• The amount of CPU needed to do the server work - this is primarily a single threaded activity and can only be improved by single processor rates.
• Communications bandwidth which can be variable depending on time and location.
• Browser performance with FireFox considered to be generally faster than Internet Explorer (IE).

Factors to address

Cache for Confluence is:

• Most impacted by page construction techniques to reduce processing load.
• Addressed by reducing the size of the rendered text and images.
• Addressed by browser options (caching) and by pages that best optimize browser capabilities (like caching).

Server processing

It is important to note that all the elements of a page must be rendered even if portions of the page are not displayed initially. For instance, if you use constructs that have tabs or have expand and contract sections, all the data in those sections still must be rendered. Generally, the display of the data is controlled by the browser with no further interaction with the server (an exception is delayed rendering discussed below). This means that pages with a large amount of data that is gathered and processed but not shown immediately to the user, may be wasted processing if the most likely user interaction is to not look at that tab or hidden section.

...

...

If you have a lot of charts that are relatively static (only change occasionally), the best approach is to save the chart image as an attachment and re-use this image for subsequent viewing. This is easy to do:

• Add the following parameters to your chart macro:
  • attachment=your attachment name.png - this stores the chart image as an attachment to the page (or optionally another page)
  • attachmentVersion=keep - this tells the chart macro to only render the chart data and redraw the image if the attachment referenced by the attachment parameter does not exist
• How can the chart be regenerated? Just delete the attachment and view the page to get it to regenerate the attachment.
• Should I use the cache macro too? No, not in this case unless there is some other reason to use it on the page.

...