Self-Optimizing Runtime Dashboards

When creating a runtime document unused component sections are deleted to reduce the dashboard size and to improve performance. Therefore, an ESM contains components that can work and exist together (some components cannot share an Interactive Reporting document with others; for example, Query Limits and Quick Query Limits) without burdening the runtime with unused resources, such as code, language strings, and sections. The ESM is a developer release of the Interactive Reporting document and is less efficient, but the runtime is slim and provides the configured functionality.

Runtimes created for production should use the packing option. See Packing JavaScript Feature.

Runtimes created for unit testing experimental Interactive Reporting documents, those containing new JavaScript in the form of custom components or in 1100 Custom (see 1100 Custom), should not be packed as the diagnostics that tracing enables is used.