ok, thanks for the feedback. yes, integrating jsreport studio login into the sso flow would be great, we will analyze this and based on that we will define a priority for it.
would you have any recommendation on size of instance that we should be using in production
There is no way for me to predict this. Try some production load on your test sever and find the best fitting VM size.
Be ready to scale up and down in the production.
? I can definitely also see a lag between the time the node express data extract has all the data and when it is delivered to the report preprocessing script as a json array. I did also import the axios library into js reports to replace the request utility and that seems to work on large datasets without having to specifically code anything to stream data. Would you have any concerns on me doing that?
I am a bit lost. Please try to describe exactly what steps do you do to reproduce the error.
You are trying to upload the jsreport export zip, using the studio, and it fails on one server and not on the other?
I am afraid I don't have a hypothesis why this could happen. Maybe you have a proxy before jsreport that could modify the request?