Topics created by gupta-nitish

Currently, your only option is to fork the scheduling extension and do the change in code.

We will make the behavior configurable in future release.
https://github.com/jsreport/jsreport/issues/650

i replied in the github issue, let's do future comments there

The node process likely reaches the 1.5GB memory and starts to run GC.
You should increase the memory limit for node.js process using --max-old-space-size flag

node --max_old_space_size=6096 server.js

or if you use jsreport cli set environment variable

NODE_OPTIONS="--max-old-space-size= 6096"

and run

jsreport start

This will get propagated by default just to the main process. If you use dedicated-process or http-server strategy for templating engines/scripts, you need to set also this config

"templatingEngines": { "timeout": 1000000, "strategy": "dedicated-process", "forkOptions": { "execArgv": ["--max-old-space-size=6096"] } }

However, the in-process strategy will give you the best performance, because it avoids serializing and deserializing of such giant JSON between processes.

With increasing the memory limits, I am able to produce 200MB output with 15mil records.

You shouldn't mix jsreport and jsreport-core together I think.
If you have questions about jsreport-core, please use its github repository jsreport-core.

This forum is for jsreport product users and we don't want to mix it here together.

hi! for sure there is a way to use it without studio, however we don't have docs for use each jsreport extension with just core, however you can do the same that studio does by using the http api that jsreport exposes, and you can check real example of how to do it by checking the studio code of scheduling and see how it executes the POST request to save or run a schedule