Hi Martin :

Admin site SN Master Tree needs to link the result similar to the legacy site as shown in the video below. Please create a DevOps item.

SN Master Tree linking ability (11-Mar-22).mp4 5.94 MB • Download

Thanks,

Paul

Hi Paul,

DevOps bug https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1631 was created.

Thanks,
-Martin

Hi Paul ,

This task is done and uploaded on stagin.islg. Please check and confirm.

https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1731

cc: Martin Harsh  

Hi Piyush :

It looks good, but I have a following question before I can mark it complete.

Martin : some branches that are buried under a lot of parent branches take up to 10-15 seconds to load - is this a wider issue of the admin site or something localized to this tool?

Thanks,

Paul

Hi Paul , do you have an example of this?

Hi Piyush and Harsh , can you help us understand if the delay is caused by a heavy SQL query, or perhaps the actual routine building/seeking the tree data? Do you think we could make potentially good performance gains if we include this as an item in a future sprint?

Thanks,
-Martin

Hi Harsh , based on Paul's video above, can you give more insight as to what is happening during the 10 seconds wait?

I.e.: how much time is spent:

Thanks,
-Martin

Hi Martin ,

The HTML is taking time to rendering data. When we built this tool that time this requirement was not there. 

so currently, We need to render one by one branch to locate destination. Due to this reason it is taking 3 to 4 second more time.

The SQL Query is working fine.

Hi Martin :

There are many branches that will be buried deeper compared to the example video above. Below is how snappy the legacy site was using the same keyword tantamount; I would like to not lose any efficiency compared to the legacy. Could you investigate a way to be as instantaneous as the legacy site?

SN Linking speed on legacy (24-May-22).mp4 2.11 MB • Download

Thanks,

Paul

Hi Harsh , would the solution be to rewrite how the HTML is rendered? What type of effort would be required (high-level estimate is ok)?

Paul : I do not think we will be able to have instantaneous results like the Legacy app, given that we use heavier components in the user interface and have a more complex database structure. But we should aim to cut the time by at least half of what it is today.

Thanks,
-Martin

Paul and Martin ,

In Legacy site they haven't render action menu within branch and legacy application render the UI in simple way.

In Our rebuild application, the most of time is taking render the html due to JS script and CSS with Action Menu (Provided by Industrial team).

We will definitely look into it and try our best to increase the performance.

Hi Paul ,

I have created DevOps item https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1912 to track this effort.

-Martin

Hi Paul ,

This item is marked as Completed in basecamp, but it is still pending in DevOps.
Do you know why?

Thanks,
-Martin

Hi Martin :

Maybe we should've created a separate BC post, but even though my initial request is done (linking each SN entry to the SN Master Tree where it appears), DevOps 1912 is about the rendering speed of each entry link to the SN Master Tree especially if an entry is buried under multiple sub-headings as highlighted below. I'll reopen this BC to avoid confusion.

image.png 25.1 KB • Download

I put three "related" items to focus on SN rendering speed issue below.

image.png 8.74 KB • Download

Thanks,

Paul