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.

Sign up for GitHub

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

Jump to bottom

GUI takes a long time to show details of some entities #97

Closed
ZackHill05 opened this issue Oct 3, 2019 · 16 comments
Closed

GUI takes a long time to show details of some entities #97

ZackHill05 opened this issue Oct 3, 2019 · 16 comments
Assignees
@arawinters @barrycaceres @antaenc
Labels
performance Correct behavior, but slow performance

Comments

@ZackHill05
Copy link

When clicking on an entity to get more details in the GUI, it takes 40 seconds before the details come up. The screen is blank until the details come up, so to the user it looks like bringing up the details "didn't work".

When the details do come up, it takes another 40 seconds to show the relationships for this entity.

Two things:

  1. It would be nice to have some indication that the GUI is still working on bringing up the information.
  2. Does the database need to be tuned to make the detail display faster? Do indexes need to be added? I ask because for this one person it always takes this amount of time, but for most the details and relationships come back quickly. Another interesting thing about the relationships coming back so slowly for this one is only 4 relationships are returned. Getting details on another person with 4 relationships comes back quickly.
@docktermj
Copy link
Contributor

@arawinters Part of this is really a https://github.com/Senzing/entity-search-web-app issue. When it comes to performance, I refer to @antaenc.

@docktermj
Copy link
Contributor

@ZackHill05 Would it be OK if I opened up a separate issue for your "thing #1" in the https://github.com/Senzing/entity-search-web-app repository? (Or if you want to, that's OK with me)

@ZackHill05
Copy link
Author

ZackHill05 commented Oct 3, 2019 via email

@docktermj docktermj mentioned this issue Oct 3, 2019
Closed
@docktermj
Copy link
Contributor

New issue: senzing-garage/entity-search-web-app#69

@antaenc
Copy link
Contributor

antaenc commented Oct 3, 2019

Hi Zach,

Are you referring to the standard Senzing web components in a browser or the i2 integration?
No, additional indexes are not required.

The interesting comment is it only happens for one person and not others:

  • Is the person this is slow for pulling back a different entity and relationships to other users where it is faster?
  • Are they in the office and on a more local network as opposed to being at home or travelling on a different slower network?
  • Anything else technically to explain why they might be slower?

Ant

@barrycaceres
Copy link
Contributor

@ZackHill05 does the entity take a long time to display for the first one? the first 8? or for all of them?

I ask because there is some initialization that occurs on the first entity search.... and then there is some initialization for each thread (usually there are 8 threads for handling entity searches). Trying to pin down what the cause might be.

@arawinters
Copy link
Contributor

arawinters commented Oct 8, 2019 •
edited
Loading

@barrycaceres I left a comment on this issue on a different ticket. senzing-garage/entity-search-web-app#67
It's a regression in the spinner behavior and is closely related to the graph api request. Though the regression only pertains to the spinner behavior and not the load time of the api request itself. what's happening is that the spinner is disapearing after the initial entity request, but before the graph api request is fullfilled, the time in between is the time spent waiting for the find network endpoint request.
it is most noticeable on the first request, subsequent requests to load that entity are displayed fairly quickly.

@docktermj
Copy link
Contributor

@ZackHill05 Just checking in. Did we resolve this to your satisfaction?

@ZackHill05
Copy link
Author

@docktermj not yet, but my team lead has asked me to make this my last priority with Senzing. If you need to close this issue, that's fine. I'll re-open when I have more time.

@docktermj
Copy link
Contributor

@ZackHill05 We'll keep it open so that we know it's an issue. (cc: @barrycaceres )

@docktermj docktermj added enhancement New feature request performance Correct behavior, but slow performance and removed enhancement New feature request labels Jan 12, 2020
@ZackHill05 ZackHill05 mentioned this issue Feb 26, 2020
Closed
@barrycaceres
Copy link
Contributor

I am pretty sure this is addressed in Senzing 1.15.2 with the performance improvements for obtaining entity networks.

@barrycaceres
Copy link
Contributor

Zack -- do you want me to close this issue, or would you like to upgrade to 1.15.2 and confirm first?

@ZackHill05
Copy link
Author

ZackHill05 commented May 20, 2020 via email

@barrycaceres
Copy link
Contributor

Zack -- any progress on this? Did you get a chance to test the upgrade to v1.15.2? Version 2.0.0 is being/has just been released this week (just an FYI).

@ZackHill05
Copy link
Author

ZackHill05 commented Jul 17, 2020 via email

@barrycaceres
Copy link
Contributor

barrycaceres commented Aug 4, 2020 •
edited
Loading

Zack,

If it is no longer an issue, would you mind closing this issue? If I don't hear back in two weeks, I can go ahead and close it. Just trying to tidy things up on our open issues list.

Thanks!

-Barry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arawinters arawinters

@barrycaceres barrycaceres

@antaenc antaenc

Labels
performance Correct behavior, but slow performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@docktermj @arawinters @barrycaceres @antaenc @ZackHill05