[COMPASS-4431] Compass for Mac extremely slow on Analyze schema Created: 01/Oct/20  Updated: 03/Oct/23  Resolved: 14/Oct/20

Status: Closed
Project: Compass
Component/s: Performance, Schema
Affects Version/s: 1.22.1
Fix Version/s: No version

Type: Bug Priority: Major - P3
Reporter: Mareks Zirdzins Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mac


Issue Links:
Duplicate
duplicates COMPASS-4125 d3-tip breaking out of vdom Closed
Story Points: 3
Documentation Changes: Not Needed

 Description   

When performing scrolling on analyze schema page in Compass for Mac, it hangs for several seconds on each scroll before it continues. The more you use it, the slower it gets up to a degree where no action with Compass is possible without quitting the app.

 

Colleague who uses Windows machine reports similar issue.



 Comments   
Comment by Massimiliano Marcon [ 14/Oct/20 ]

Thank you mareks.zirdzins@accenture.com for digging into the details of the problem and figuring out the issue that causes it! This looks the same as COMPASS-4125 so I am closing this as Duplicate.

We'll get COMPASS-4125 fixed as soon as possible.

Comment by Mareks Zirdzins [ 06/Oct/20 ]

I think I found the core issue. It seems to be in the mouse over value. It looks like for larger dataset Compass has difficulty calculating the tooltip value and that one runs on main thread, blocking everything else. 

If I scroll placing mouse cursor in the middle whitespace between property names and values, it does not lag. But if I happen to have it on the left side, it gets to a halt quickly, apparently queueing up calculations of each mouse over tooltip that I ran over until it freezes.

Comment by Mareks Zirdzins [ 06/Oct/20 ]

Just to directly answer your question, my last, most annoying experience is with around 2000 documents, that has nested structure with around 80 properties that have a document with couple of sub-properties each. It is basically a contract document with things like address, postal code, name, surname, etc. Nothing fancy. But same is with smaller documents. I think if list of found properties goes around 3 screens tall, the scrolling lag (inability to scroll for 5 seconds or so) will be first to notice, then, for bigger document property count, full halt lag will become apparent.

Comment by Mareks Zirdzins [ 06/Oct/20 ]

The same problem is with collection of any size, even several hundred documents. One thing I noticed is that the bigger the list of properties that the analysis found, the slower it gets. And the more you use (scroll, click) in the Analyze results screen, the slower it gets, and in couple of minutes you will go to full halt when only option is to force closing the app.

I cross checked with my colleagues, and they have the same problem with windows version of Compass, so it is some kind of general thread management or memory management issue in the codebase.

It does not need any extensive testing, its not some kind of corner case. Simply press Analyze on any meaningful dataset and try just scrolling with mouse scroll and clicking on properties to view them to get the freezing in first 5 seconds or so, which will just become worse and worse with every second from that point on up to a full halt, where even mouse over tooltip will lag up to minutes, no scrolling possible, you cant even close the tab to open a new one.

Comment by Massimiliano Marcon [ 06/Oct/20 ]

mareks.zirdzins@accenture.com how big is the collection? how big are the documents?

Generated at Wed Feb 07 22:36:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.