|
|
Rank: Newbie
Groups: Member
Joined: 1/7/2015
Posts: 7
|
Hello,
We have been using the 2017 version of the HTML TO PDF product for 5 years in Azure Cloud Services (Classic) with very minor issues. However, we would like to move our service to Azure App Services. We tried running our app in App Services instead of Cloud Services. Unfortunately, we received many complaints about timeouts and long response times. This was not happening in Cloud Services. Also, initial pdf conversion takes too long in App Services, however, we resolved this using a job that converts empty string to html every 2 minutes.
We are thinking of upgrading to latest version but we have no idea whether the problems will be resolved or not since we cannot use the trial version in production. Is it possible to use the trial version in production without red warning at the bottom of the generated pdf page? Or can we have refund in lets say 2 weeks, If it does not work for us.
Thank you,
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Hi,
We can provide a two weeks license to you so that you can try it in your enviornment.
When you use Azure App Service, make sure you do not use shared plan (used dedicated or isolated servers). Additionally, the new version uses a much newer browser engine --- which also means it's larger and can consume more resources. So you may want to try to configure your server with more resources if you continue to run into problems.
We will PM you with a trial license key.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 1/7/2015
Posts: 7
|
Hello,
Thank you very much for the trial key.
We have been using the latest version in production .Net Core 3.1 environment in Azure App Services (P3V2) for couple of days. Average request count is 30 - 50 Html To Pdf conversions per minute and it is working without problems.
We will continue testing for couple more days, then migrate all our services.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Glad to hear that!
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/8/2017
Posts: 64
|
eo_support wrote:
When you use Azure App Service, make sure you do not use shared plan (used dedicated or isolated servers). Additionally, the new version uses a much newer browser engine --- which also means it's larger and can consume more resources. So you may want to try to configure your server with more resources if you continue to run into problems.
Hi, when you say a shared plan can you be a little more specific - when you say a dedicated plan do you mean per app or just a “dedicated” plan. We have a dedicated plan (not a “shared” plan, it is a premium2v3) but it has multiple app tiers running on it https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-hosting-plans.mdKind regards Phil
|
|
Rank: Newbie
Groups: Member
Joined: 1/7/2015
Posts: 7
|
Hello, P2V3 is fine. We are using the same plan.
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/8/2017
Posts: 64
|
OK - thanks for confirming
|
|