This issue is resolved on staging.islg. Please check and confirm.
Notified 5 people
Paul Moon
Hi
Harsh
:
The loading time is acceptable now. I understand that due to some instruments missing TOC, I am not taken to the expected specific location (e.g., Article 46 in the video), so I'll leave it open until we resolve that issue.
Thanks,
Paul
Notified 5 people
Harsh Parikh,Tech Lead
Hi
Paul
,
The toc issue will take care after post launch in seprate thread. so except toc all ok then please complete this task.
Notified 5 people
Paul Moon completed this to-do.
Morgan Maguire re-opened this to-do.
Morgan Maguire,CEO
Hi
Harsh
,
Further to the video below, the issue resolved above with loading time in the Document View has not been resolved with the most recent deployed from staging.islg to app.islg. The loading times there are extremely long as they were previously on staging.islg.
Could you please ensure we perform an audit to ensure these loading issues where properly deployed in app.islg.
It seems like this issue is due to database server performance. As we run from our DEV server and the data is loading within 2 to 3 second with same amount of data.
I strongly recommended to flag this database performance issue to carbon 60 and get solution by tomorrow.
Here, I have attached reference video which run in our local server.
This issue is resolved on staging.islg. Please check and confirm.
The loading time is acceptable now. I understand that due to some instruments missing TOC, I am not taken to the expected specific location (e.g., Article 46 in the video), so I'll leave it open until we resolve that issue.
Thanks,
Paul
The toc issue will take care after post launch in seprate thread. so except toc all ok then please complete this task.
Further to the video below, the issue resolved above with loading time in the Document View has not been resolved with the most recent deployed from staging.islg to app.islg. The loading times there are extremely long as they were previously on staging.islg.
Could you please ensure we perform an audit to ensure these loading issues where properly deployed in app.islg.
Thanks,
Morgan
It seems like this issue is due to database server performance. As we run from our DEV server and the data is loading within 2 to 3 second with same amount of data.
I strongly recommended to flag this database performance issue to carbon 60 and get solution by tomorrow.
Here, I have attached reference video which run in our local server.
There is a significant difference between app.islg and staging.islg. Wouldn't that indicate there is an application issue, rather than a server issue?
Morgan
Morgan
This issue is resolved on both app.islg and staging.islg. Please check and confirm.
Thanks,
Morgan