Hi Martin :

As shown below, when I click on each SN entry from individual UIN analysis list, it takes between 15-20 seconds for SN Master List to open up whereas it used to take 5-10 seconds. Could you add to unplanned/critical and restore the speed before?

SN link from Analysis List slow (12-Oct-22).mp4 6.6 MB • Download

Please add this to unplanned/critical.

Thanks,

Paul

Hi Harsh ,
Can you investigate and make a new task under Unplanned issues?

Thanks, 
Martin 

Hi Harsh ,

I created task https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/2196 to track this.

-Martin

Hi Paul and Martin ,

I checked and update the stored procedure performance. Now,, it is taking up to 10 to 12 seconds to load in SN. 

As I mentioned earlier, the page will render based on how deep the child branch and also each branch is rendering with Action menu. Due to this reason to render data  up to nth level it is taking near about 10 to 12 second.

Hope this is OK.

Hi Harsh :

The same example from the first video still takes 20 seconds to load as shown below. It shouldn't take more than 5-10 seconds max to load each entry regardless of where the entry is located.

SN link from Analysis List slow 2 (3-Nov-22).mp4 1.21 MB • Download

Martin : is this we can further research on or no?

Thanks,

Paul

Hi Paul ,

My understanding is that when the new Subject Navigator was designed, we did not plan on linking to it from the Analysis List.

With the way the current HTML template has been constructed, each level down in the SN requires a trip to the server, which will then query SQL and return the direct children.

The deeper the node is, the longer it will take to get to it. I think the impact is felt even more when linking from the Analysis List, as there are no user interactions happening while the SN page performs all the necessary drill-downs to get us to the right node (i.e.: it "feels" even slower, because the user does not participate in clicking on the nodes).

It would be beneficial to all meet and brainstorm on possible ways to improve performance. But our feeling is that it will probably require a rewrite of the Subject Navigator logic (which is likely to include the HTML template, the App service and even perhaps the SQL queries to the database).

Hi Martin :

Please schedule a meeting when Harsh comes back from his time off to discuss this.

Thank you,

Paul

Hi Paul ,

I have scheduled the meeting on Dec 7 at 8am your time.

Thanks,
-Martin

Hi Martin :

Did we end up creating a DevOps for this? If not, should we postpone this until we look at how we store HTML documents later this year?

Thanks,

Paul

Hi Paul ,

If I recall our conversation, we did agree that this was going to be a relatively large project, as we anticipate that all layers of the application (from the frontend, to the app server, to the SQL server) will need to be re-engineered in order to gain significant performance.

Is this what you recall? If so, I will create a DevOps item to re-engineer how the SN is constructed and populated on screen.

Thanks,
-Martin

Hi Martin :

Yes, that's what I recall as well. I wanted to ensure that it is logged somewhere as we move away from this BC.

Thanks,

Paul

Hi Paul ,

I have created https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/2533 for the re-engineering of the SN tree population.

Thanks,
-Martin