The process allocation link you gave does not give any information on chrome-pool strategy, And even when I tried to use dedicated-process strategy , debug information still shows chrome-pool strategy being used. Why is that ?
Posts made by Harpreet Saluja Wali
-
RE: Multiple concurrent requests , timeout problemposted in general forum
-
RE: Multiple concurrent requests , timeout problemposted in general forum
Thanks for the tip !
I tried Chrome pdf now , and it does work faster than electron. What can I do improve performance still ? Current config is
"chrome": {
"timeout": 40000,
"strategy": "chrome-pool",
"numberOfWorkers": 4
}I could not find in docs , what is the difference between Chrome-pool and dedicated strategy ? Are there any other strategies as well ?
-
Multiple concurrent requests , timeout problemposted in general forum
I am using the electron recipe to create PDFs using HTML and JSOn data. Each PDF rendering request was approximately taking 2 seconds , to improve performance now I am sending all requests concurrently bombarding the JSreport server with config as 8 workers, so now approx 8 PDFs are simultaneously being created improving the overall time. But the issue is , the rest of the requests waiting to get a worker accumulate the time and they time out. How can I fix this issue ?