Topics created by Sesughter01

So imagine a dataset that generates a template with 20 to 30 full content in letter-size pages including some infographics

it is hard to tell you how to optimize something i don't have full visibility but it seems to me that in this case the loop is not the slowest part, but rather the pdf generation handled by chrome (assuming you are using chrome-pdf recipe), which is slow at generating a table with a lot of rows.

if you render the template in the studio with the same data that the api send, what do you see in the studio profile? that should give you some hints about what took the most part in the render.

the component should be there if you installed jsreport from npm, are you installing this way?

Yes, you need to do what it says. Close the dialog, switch to the "Full profiling" and wait for the incoming request to pop up.

The helper functions and templating engines run in a separate sandbox without DOM. You can reach DOM inside <script></script> tag.

Please see the complete description here
https://forum.jsreport.net/topic/566/javascript-on-a-script-page