How to activate in-process strategy?

msageryd

The log says

Converting with chrome HeadlessChrome/76.0.3809.132 using dedicated-process strategy

My config says:

  "templatingEngines": {
    "numberOfWorkers": 2,
    "timeout": 300000,
    "strategy": "in-process",

What do I need to do to activate in-process strategy?

jan_blaha

Templating engine is something completely different than chrome pdf recipe...

The chrome-pdf has its own strategies for conversion, check the docs for it.
https://jsreport.net/learn/chrome-pdf#reuse-chrome-instances

msageryd

Thanks.
Is there any way of knowing which engine strategy is used?
I assume that I am using "in-process", but I'd like to know for sure. Didn't find anything in the logs.

msageryd

I want speed =)
As I'm in complete control over my templates, I'm going for speed instead of process isolation.
What more can I do besides choosing in-process for the engine strategy?

Do you know which the worst bottlenecks are?
Should I throw more memory, more cpu-speed or more cpu-cores at jsreport to make it faster?

jan_blaha

Is there any way of knowing which engine strategy is used?

It should be written in the output loogs when jsreport is booting.

Do you know which the worst bottlenecks are?

You should see the timing for specific parts of rendering when you hit debug in the studio.
In most of the cases the chrome makes the most of the time and other optimizations are not so much worth it.
More CPU speed should help though.
However, take your time and test what works the best for you.