Topics created by tyler-shuhnicki

I've attached an image and profile logs to show output - I believe this confirms Chrome is the bottleneck.

Yes, it is.

are there any specific pitfalls to avoid when it comes to using a table?

The long tables are typically slowing chrome rendering, but honestly, chrome is for us black-box just like for you, so I don't know how to trick this.

Thanks for all you do!

You are welcome. I'm sorry I'm not helpful here. Good luck!

{
.
.
"workers": {
"numberOfWorkers": 2
},
"extensions": {
"chrome-pdf": {
"launchOptions": {
"args": ["--ignore-certificate-errors", "--no-sandbox"]
}
}
}
}

did work for v4

I apologize, I didn't have time to play with lambda using docker yet.

Hey Jan,

Strangely, I re-deployed the code via elastic beanstalk and it worked as expected without any errors. I will update this thread if it appears again.

Thanks!
Tyler

Thank you much, Jan!

Apologies, as I'm pretty inexperienced with Node.

I've taken the node.exe file from C:\Program Files\nodejs and placed it in the jsreport folder. It is in the same directory as server.js, data, node_modules, etc.
Running the command "node server.js" from the cmd prompt yields the response "cannot find module 'semver'.

Thanks Jan!

I've emailed over the template as requested.

Thanks!
Tyler

Thank you. I wrote you mail back.
Let's continue over email to avoid exposing some confidential information.
We will write the resolution afterward here.

It is very helpful to know you can restart the service through the service manager (or the studio). It's certainly much more straightforward and reliable for a deploy. Thank you much!

I did check the InputRequestLimit configuration and it works for me fine.
Does this fail only for big reports?
If yes, can you check the memory consumption?
It can be problem with node memory.

@explorer855 thanks for sharing your case, it is good to know new kind of problems that users can face.