Managing Report Package Sizing Considerations

Designing report packages with an appropriate size and level of complexity helps promote responsive performance and a smoother user experience.

When you open a report package, the service loads its structure and all associated doclet files into memory. Large report packages or unusually large individual doclets can require additional processing time for operations such as:

• Opening the report package or individual doclets
• Refreshing available content
• Checking in doclets
• Rendering previews
• Generating review instances
• Publishing reports

The following factors can affect report package performance:

• Overall report package file size
• Size of individual doclets
• Number of doclets
• Number of reference doclets
• Amount of refreshable reporting content
• Number of variables
• Embedded images and media
• Depth of the report hierarchy

A report package that contains numerous refreshable objects, images, charts, and embedded content generally requires more processing than one that consists primarily of narrative text.

Review both the overall report package size and the size of individual doclets when assessing performance. An unusually large doclet may require optimization even when the overall report package size is manageable. Consider reducing embedded images and media, removing unnecessary content, or dividing a large doclet into smaller doclets where appropriate.

Slow opening, refreshing, doclet check-in, preview rendering, review-instance generation, or publishing can indicate that the report package or individual doclets should be reviewed for optimization.