Performance and Logging

Performance and Memory Consumption

We do our best to make the export as efficient as possible, however, creating PDF documents IS a memory- and cpu-intensive task and will always be. We recommend the following measures:

• Make sure to tune Confluence appropriately (Cf. http://confluence.atlassian.com/display/DOC/Performance+Tuning).
• Allocate more memory to Confluence (but avoid swapping under all circumstances).
• For larger Confluence installation limit the number of users who are allowed to create exports with Scroll. This can be done by granting the 'Export Space' permission only to certain number of users.

Configuring Scroll Logging

In order to avoid Scroll's internal PDF exporter to clutter you log file, we recommend to add the following to Confluence's Log4j configuration file. (You will find the log configuration file in your Confluence installation directory under <CONFLUENCE-INSTALL>/confluence/WEB-INF/classes/log4j.properties)

:
## This is the logging configuration for Scroll: -------
log4j.logger.com.k15t.scroll=INFO, confluencelog
log4j.additivity.com.k15t.scroll=false

log4j.logger.com.k15t.scroll.core.export.impl.Fop09Exporter=ERROR, confluencelog
log4j.additivity.com.k15t.scroll.core.export.impl.Fop09Exporter=false

log4j.logger.org.apache.fop.fo.FONode=ERROR, confluencelog
log4j.additivity.org.apache.fop.fo.FONode=false

log4j.logger.org.apache.fop.fo.properties.PropertyMaker=FATAL, confluencelog
log4j.additivity.org.apache.fop.fo.properties.PropertyMaker=false

log4j.logger.org.apache.fop.image.FopImage=FATAL, confluencelog
log4j.additivity.org.apache.fop.image.FopImage=false

log4j.logger.org.apache.fop.layoutmgr.BreakingAlgorithm=ERROR, confluencelog
log4j.additivity.org.apache.fop.layoutmgr.BreakingAlgorithm=false
## ------ Scroll logging configuration.
:

More information about logging Confluence can be found here: http://confluence.atlassian.com/display/DOC/Working+with+Confluence+Logs