Uploaded image for project: 'Pentaho Reporting and Pentaho Report Designer'
  1. Pentaho Reporting and Pentaho Report Designer
  2. PRD-4921

As a reporting end user, I want the performance of CSV, HTML and Excel outputs to take less time to generate.



    • Type: Improvement
    • Status: Closed
    • Severity: High
    • Resolution: Fixed
    • Affects Version/s: 5.0.0 GA (5.0.0 GA Suite Release)
    • Fix Version/s: 5.1.0 GA
    • Component/s: Report Generation
    • Labels:
    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.


      Many of our customers use PIR as a sort of data-export tool to get data from the data-warehouse into Excel. However, the reporting engine always performs a full layout run on these exports, even though in this particular use case the styling is of secondary concern.

      Normally, the reports used for export are plain reports, with no subreports or advanced style-expressions or formatting functions attached to them.

      Lets provide an new, limited purpose output target that exports reports by ignoring any of the advanced layout calculations. As the reporting engine spends between 85% to 95% of its time in the layouting stage, if we cut out the layouting and use a simpler, template based approach, we can increase the reporting performance by at least 5x if not the maximum of 10x the original processing time.

      The templates can be automatically pre-computed by the engine based on the report's layout.

      If the report in question contains subreports or other advanced features, we can print a warning in the log and fall back to the original, slower but complete CSV and Excel exports.

        PractiTest Integration


            Issue Links



                gdavid Golda Thomas
                tmorgner Thomas Morgner
                2 Vote for this issue
                9 Start watching this issue