Hi Martin :

As shown below, the "Expand all" function under Subject Navigator is very sluggish. I understand "Expropriation" and "Fair and equitable treatment" examples in the video contain a large number of entries, but it shouldn't take a minute or 90 seconds to load the results. At most, any "Expand all" should load within 10 seconds. I'll prioritize it once this becomes a DevOps item.

Expand all performance (7-Mar-22).mp4 5.78 MB • Download

Thanks,

Paul

Hi Paul ,

I created DevOps item https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1609 for this.

--Martin

Hi Paul ,

When you click on Expand All then application is going to open all branches up to nth Level and if the branches will deeply more and more then it is always taking time to render all branches  in page on one click.

So, We need to change the way. Is it Ok that we can open only first level branch while user click on Expnad All link.

Martin  

Hi Harsh :

As discussed during the meeting, opening the first branches only is not acceptable for this function. Let's see what you could come up with the research during the next sprint.

Thanks,

Paul

Hi Harsh and Hiren :

I tested this deployed item https://dev.azure.com/tologix/ISLGRebuild/_sprints/backlog/ISLGRebuild%20Team/ISLGRebuild/Sprint%2038?workitem=1609 on app.islg, but some Expand All options (e.g., E or J) take 15-17 seconds to load. It is an improvement, but considering we are now opening only the first level branches, it should load within 5 seconds. I've reopened DevOps.

Expand all performance 2 (14-Sep-22).mp4 664 KB • Download

Thanks,

Paul

Hi Paul ,

I agree that for the amount of data loaded in the page, the wait time seems too high.

Do you want us to continue working on this in the current sprint? If so, this will need to go against Unplanned hours, or we will need to make room by dropping another item.

Harsh : I expanded "A", and it took 29 seconds. This is about one second for each SN entry. Can you help Paul and I understand where the slowdown is, and what our options are to further improve this?

Thanks,
-Martin

Hi Martin :

Let's move the reopened https://dev.azure.com/tologix/ISLGRebuild/_sprints/backlog/ISLGRebuild%20Team/ISLGRebuild/Sprint%2038?workitem=1609 to Sprint 40. Whatever we need to do can wait for now.

Thanks,

Paul

Hi Paul ,

It has been moved to the top of our backlog, and we will tackle in the sprint 40.

Thanks,
-Martin

Hi Martin   and Paul ,

In Last sprint, We worked on Subscriber side. We haven't worked on Admin Side. On Subscriber side, any user click on Expand All then we are loading only first level branch now.

Hi Paul ,

I have prefixed https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1609 with "Subscriber SN" and change its state back to "Installed in Production".

If we want to also improve SN tree under Admin, I think we should create a new backlog item for it.
Let me know if you'd like me to do that.

Thanks,
-Martin

Hi Martin :

Ok, let's create another backlog item for the admin site then.

Thanks,

Paul

Hi Paul ,

https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/3026 was created to track SN expand all performance on the Admin side.

Please prioritize accordingly.

Thanks,
-Martin

Admin site fix has been implemented as well.