Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browser performance issue in HierarchyWidget #148

Open
Pooya-Oladazimi opened this issue Oct 11, 2024 · 2 comments
Open

Browser performance issue in HierarchyWidget #148

Pooya-Oladazimi opened this issue Oct 11, 2024 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@Pooya-Oladazimi
Copy link
Collaborator

Every time I open the HierarchyWidget, my Browser starts to lag, and the response is slow. It looks like something is stuck in the loop or some API call got stuck.

Does it happen to you also? @jusa3 @VincentKneip

Browser: Firefox v131.0.2
OS: Ubuntu 22.04

I noticed this in the console:
Screenshot from 2024-10-11 15-27-37

@Pooya-Oladazimi Pooya-Oladazimi added the question Further information is requested label Oct 11, 2024
@rombaum
Copy link
Collaborator

rombaum commented Oct 14, 2024

Vincent and I spotted a loop in this terminology. In the past the hierarchy was not loading. He interrupted the loop before the first cycle but he added this information to the log. But he could also give you more details. ;)

@VincentKneip
Copy link
Collaborator

The lag could have multiple reasons:

  • The stories of HierarchyWidget are much bigger than stories of other widgets in general
  • The SagePub story illustrates how the widget deals with cyclic trees, throwing the warning on the console
  • OntoPortal requires providing an api key to use their API. As no key is provided in the respective story by default, the query results in an Axios error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants