Topics created by Rommel Manalo

hi! we now (since jsreport 3.9.0) provide arm builds for our docker images, this resolves the issue with Apple Silicon hardware. the full details to run on that hardware are specified here

Yep it works.. thanks, these needs a blog or recipe entry please

Thanks for the info. i will try that one

After some thought, the jsReportClient is really the issue here. Actually there is a setting jsRepoClient that i overlooked, https://jsreport.net/learn/nodejs-client
at the bottom of the article named "Handling request timeout".

So my issue is resolved here, and it can be tagged as resolve if necessary

ow.. the document of jsreport-mongodb-store, updates in relation to it.. good job.

Yes, this is expected. With the default config, and 100 parallel requests, jsreport creates ~100 processes for rendering. Please try to add this config. It will limit the number of used worker processes.

{ "chrome": { "strategy": "chrome-pool", "numberOfWorkers": 5 }, "templatingEngines": { "strategy": "http-server", "numberOfWorkers": 5 } }

https://jsreport.net/learn/configuration
https://jsreport.net/learn/chrome-pdf#reuse-chrome-instances

This should make your parallel test passing.
If not, maybe you should consider putting a full webserver like nginx before the jsreport and configure there throtling and delayed requests execution during peak.

Im sure this is is a singleton. Only one instance of jsReport is running, i even put this on global object of nodejs to make sure i did the init once and just re-use the same instance of jsReport. It will be hard to scale up jsReport, with this 800 samples on 100 virtual users it dies.. I thought there is a separate process for running the renderer, it even have a poor thoughput, with 1 operation per minute!! Remember my machine is alienware, a gaming laptop with huge memory and cpu. So this operation and performance is very poor on my setup.. Not sure what is the problem