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

Improve performance of user federation #1278

Closed
LucaCinquini opened this issue May 17, 2016 · 4 comments
Closed

Improve performance of user federation #1278

LucaCinquini opened this issue May 17, 2016 · 4 comments
Assignees
Milestone

Comments

@LucaCinquini
Copy link
Contributor

Who: Luca

CoG must periodically update the user status (project tags and project memberships) from across the federation. This is an expensive operation which involves querying all the other federated CoG sites. This happens whenever one of these two conditions happens:

o The user logs into CoG
o A timeout equal to 3600 has passed since the last update (even if the user uses an established cookie session, without logging in again)

Currently, the user status update is executed synchronously, which will cause unnecessary delay when the user starts using CoG.

@LucaCinquini LucaCinquini self-assigned this May 17, 2016
@LucaCinquini LucaCinquini added this to the Release 3.6 milestone May 17, 2016
@LucaCinquini
Copy link
Contributor Author

This operation now happens in a separate python thread, i.e. asynchronously. It still happens when one of the two conditions above is met.

Note that as an additional bonus, the code now deletes user membership in groups that cannot be found, such as for example "mom5_in_nems" (because the project has been deleted, renamed, or made private at its local site).

@murphysj
Copy link
Contributor

How would I test this? Should you just close it?

@LucaCinquini
Copy link
Contributor Author

You could look at the log files and see that in the background CoG is still querying the other sites for updated information, while your page has finished rendering already.
Otherwise you can just close it I think
thanks, L

On May 26, 2016, at 9:10 AM, Sylvia Murphy notifications@github.com wrote:

How would I test this? Should you just close it?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #1278 (comment)

@murphysj murphysj added Test and removed Test labels May 26, 2016
@murphysj
Copy link
Contributor

I looked at the logs, but everything happened so fast, I could tell what happened first. I'll trust you on this one. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants