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

Improvement of communication with external graphs #3824

Open
3 tasks
chenejac opened this issue Feb 20, 2023 · 1 comment · May be fixed by vivo-project/Vitro#378
Open
3 tasks

Improvement of communication with external graphs #3824

chenejac opened this issue Feb 20, 2023 · 1 comment · May be fixed by vivo-project/Vitro#378

Comments

@chenejac
Copy link
Contributor

chenejac commented Feb 20, 2023 •
edited
Loading

Is your feature request related to a problem? Please describe.
It looks performance in communication with external/remote graph bases is quite low. This task is to improve that.

Describe the solution you'd like

  • The analysis of testing performance
  • Conduct analysis of the code which might be bottle neck (time stamps for operations)
  • Improve the performance

Additional context
Testing performance analysis from DSpace community
@chenejac chenejac converted this from a draft issue Feb 20, 2023
@chenejac chenejac moved this from Needs Triage to Todo in Semantic web features improvements Feb 20, 2023
@chenejac chenejac changed the title Detecting bottle neck in communication Improvement of communication with external graphs Feb 20, 2023
@chenejac chenejac added the Low label Feb 20, 2023
@chenejac
Copy link
Contributor Author

Conclusions from discussion:

  • We might try to speed up http communication by using some contemporary libraries
  • Frequency of firing SPARQL queries should be optimized (all requested data for one page in one SPARQL query instead of many SPARQL queries)
  • We might consider using Solr for fetching information in some cases

@chenejac chenejac removed the Low label Feb 22, 2023
@michel-heon michel-heon mentioned this issue Feb 22, 2023
Open
@chenejac chenejac linked a pull request Mar 7, 2023 that will close this issue
Network latency correction between Vitro and the outsourced tripplet vivo-project/Vitro#378
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Semantic web features improvements
Status: Todo
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Network latency correction between Vitro and the outsourced tripplet michel-heon/Vitro
1 participant
@chenejac