Posts made by visualbam

Thank you very much for taking a more in depth look! Unfortunately we have clients who do want to be able to generate reports with potentially 800-1200 pages of pretty detailed insights and do not want them to be split into multiple pdfs. We're going to be adding a batch/que system to offset the heavy load times but wanted to double check there wasn't somewhere I could shave off some minutes during generation.

Was hoping that I was using child templates / assets wrong and was doing something unnecessary to cause the load time.

Ah, I use child templates almost exclusivly. Is there a better way to achieve the description below? I wanted to make adding new sections contained and automated with using the right naming convention.

Currently what I'm doing is I create a base template file that loops through the sections. It then does the followng:

• Page break before every section so that sections don't overflow into another section.
• Set section header dynamically from section header value.
• Insert a child template based on the section name.
  • If I pass the section with a name 'some-name', it will go and pull the same named child template 'some-name.html'.
  • I also pass the section name / report type into the child template so that when I'm inside the template I can loop through the sections and access the correct section from the data I passed to the report.

The different reports I'm generating all follow the same pattern and layout so I don't need to create a bunch of chrome-pdf templates. The base-template is just there for rendering the child templates. Whenever people add new sections they only need to worry about adding one file.

File structure

root
    research folder
        section1-name (child-template)
        section2-name (child-template)
        section3-name (child-template)
    base-report (chrome pdf template)

Data object

{
    sections: [
        name: 'some-name',
        header: 'Some Name',
        ...,
        subSections: [
            {
                name: 'some-name',
                header: 'Some Name',
                ...
            }
        ]
    ]
}

Base report chrome-pdf template

{{#each report.Sections}}
    <div style='page-break-before: always;'></div>
        {{#if Header}}
            <div class="hide-data">{{{pdfCreatePagesGroup Header}}}</div>
        {{/if}}
        {{#if ../report.ReportType}}
            {{{insertChildTemplate null Name 1}}}
        {{else}}
            {{{insertChildTemplate ../report.ResourceName Name 1}}}
        {{/if}}
    {{/if}}
{{/each}}

Child-template

{{#with (lookup report.Sections parentIndex)}}
    ...
{{/with}}

@jan_blaha I'm using Merge Whole Document currently / in the example I've sent

The debug log is also too long.

https://www.dropbox.com/s/rbqm81ce4p6tmwh/jsreport-debug-log.log?dl=0

Too long to post. I'll get a successful one to render if it will help more but this is a little over 16 minutes. I was assuming the file permission thing wasn't a concern. Yeah.. the work space is kind of big. Let me know if you need that still. I can also upload the export if that helps.

https://www.dropbox.com/s/gqz5xk4algt037f/log.log?dl=0

Problem

I was wondering if long reports should take about 20 minutes at times? I run into timeout issues every now and then and was wondering if there was anything else I can do to make them render a bit faster or if this is the law of the land. Could you tell me if I'm doing something wrong with my templates, data aggregation or just doing something weird with jsreports? I'm using a slightly modified configuration from the long reports description.

I'm using jsreport: 2.3.0

{
    "httpPort": 5488,
    "allowLocalFilesAccess": true,
    "store": {
        "provider": "fs"
    },
    "assets": {
        "allowedFiles": "**/**.png"
    },
    "blobStorage": {
        "provider": "fs"
    },
    "templatingEngines": {
        "timeout": 1000000,
        "strategy": "in-process",
        "numberOfWorkers" : 16,
        "forkOptions": {
            "execArgv": ["--max-old-space-size=4096"]
        }
    },
    "chrome": {
        "timeout": 1000000
    },
    "tasks": {
        "timeout": 1000000
    },
    "extensions": {
        "sample-template": {
            "createSamples": true
        },
        "scripts": {
            "timeout": 1000000
        },
        "express": {
            "renderTimeout": 1000000,
            "inputRequestLimit": "800mb"
        }
    }
}