|
|
Rank: Newbie
Groups: Member
Joined: 5/18/2018
Posts: 9
|
Hi,
We have migrated our application recently and deployed to Production. But PdfDocument operations Like PDF generation and Merge are very slow in New Production but were OK pre production environments. Do we need to set any parameters for PdfDocument object to make PDF generation faster. Old versions of EO API is faster in old production is faster in old application( we use EO for our old application too).
The only difference I can say is we used Async and Await with new application.
Can you please suggest any settings for our problem.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Hi,
We have no way to tell you exactly why one environment is slower than the other because there are numerous factors that can affect performance. There isn't any setting on our library that can just magically increase the performance on any server. So you will have to compare the two environment to find out the difference and see if you can find out anything that triggered the issue. Once you find that out, we can then try to analyze it and see if there are any workaround you can apply to increase the performance.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 5/18/2018
Posts: 9
|
Hi, Thanks for your response.
We have huge Server resources on Production server, with average load on it. With respect to server level settings in pre-prod and prod environments, there are no changes as we took image from existing.
I would like to know if EO has any thread/task limitation and we can adjust to increase tasks to process PDF generation. and What is the limit of EO to process PDF generation.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
No. There is no single magic switch you can flip. Internally EO.Pdf relies on the browser engine from our EO.WebBrowser product, which is based on Google's Chromium project that has over 20 million lines of code. Imagining how many places in these 20 million lines of code can have performance implications? And how many switches you would need if you want to try to place switches everywhere? So issues like this, particular performance related usually requires repeated old fashioned trial and error testing and analyzing more than any other type of issues. The first thing you need to do is to find out the trigger. This is just simply hard work that you will have do and there is no shortcut around it.
|
|