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

Cache project and permissions data on startup #468

Open
benjamingeer opened this issue Mar 23, 2017 · 3 comments
Open

Cache project and permissions data on startup #468

benjamingeer opened this issue Mar 23, 2017 · 3 comments
Assignees
Labels
enhancement improve existing code or new feature

Comments

@benjamingeer
Copy link

Currently I believe project and permissions data are loaded from the triplestore and cached as they are requested. This seems to make the first login slower than subsequent logins. Would it be possible to load this data and cache it when Knora starts, the way we do with ontology data?

cc @tobiasschweizer

@benjamingeer benjamingeer added the enhancement improve existing code or new feature label Mar 23, 2017
@benjamingeer benjamingeer added this to the On Deck milestone Mar 23, 2017
@subotic
Copy link
Collaborator

subotic commented Mar 23, 2017

We probably could. This would require creating a UserProfileV1 for each registered user and storing it into the cache when webapi is started. But I don't think that this will alleviate the problem with the first login beeing slower. When a user is authenticated, then the same thing is executed for the first and any subsequent user.

But I will investigate this further (after the release).

@benjamingeer
Copy link
Author

I think it probably doesn't make sense to do this for users (because there will be a lot of them), but I was thinking it could make sense to do it for project data and permission data (which there isn't so much of).

@subotic
Copy link
Collaborator

subotic commented Mar 23, 2017

Yes, I agree. Caching projects and permissions is on my to-do list, but I wanted to finish implementing these responders first.

@subotic subotic modified the milestones: On Deck, v1.3.0 Feb 12, 2018
@subotic subotic modified the milestones: v1.3.0, v1.4.0 Mar 28, 2018
@subotic subotic modified the milestones: v1.4.0, v1.5.0 Apr 30, 2018
@subotic subotic modified the milestones: v1.5.0, v1.6.0 May 31, 2018
@subotic subotic modified the milestones: v1.6.0, v1.7.0 Jun 29, 2018
@subotic subotic modified the milestones: v1.7.0, v1.8.0 Aug 16, 2018
@subotic subotic modified the milestones: v2.0.0, 2018.11 Sep 13, 2018
@subotic subotic modified the milestones: 2018.11, 2018.12 Nov 2, 2018
@subotic subotic modified the milestones: 2018.12, 2019.01 Nov 29, 2018
@subotic subotic modified the milestones: 2019.01, 2019.02 Dec 12, 2018
@subotic subotic modified the milestones: 2019.02, 2019.03 Feb 5, 2019
@subotic subotic removed this from the 2019.03 milestone Feb 28, 2019
@subotic subotic added this to the 2019.04 milestone Feb 28, 2019
@subotic subotic modified the milestones: 2019.04, 2019.05 Mar 22, 2019
@subotic subotic modified the milestones: Priority 2, Backlog Feb 7, 2020
@irinaschubert irinaschubert removed this from the Backlog milestone Dec 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement improve existing code or new feature
Projects
None yet
Development

No branches or pull requests

3 participants