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

Modifying Users Speed Issue #402

Closed
ElementalCrisis opened this issue Jun 30, 2016 · 4 comments
Closed

Modifying Users Speed Issue #402

ElementalCrisis opened this issue Jun 30, 2016 · 4 comments

Comments

@ElementalCrisis
Copy link
Member

In Settings > User attempting to make any changes by adding/removing a user or modifying an existing user causes JMM to temporarily freeze for at least 10 seconds while your change is being processed. Using a SQLite DB on both and on 3.5.0.2 the same operations take less than a second.

@maxpiva
Copy link
Member

maxpiva commented Jun 30, 2016

Busy should be added, on big collection, every groupfilter need to be calculated for the new user. Or if the user changed the hidden categories. etc. So time maybe 10 seconds wait or 2 minutes wait, depending of the size of the collection, a processing requester should be shown on the client. Since it could take a while.

@da3dsoul
Copy link
Member

da3dsoul commented Jul 3, 2016

You should prolly add a change checker to it, to only recalculate all that if it is changed.

@maxpiva
Copy link
Member

maxpiva commented Jul 3, 2016

In fact there was a bug in there, now it'll update on category changes and new user.

Anyway, we should add a busy to JMMClient.

We might need to add a new COmmand for the commandqueue that updates groupfilters. Since it could take a while.

@maxpiva maxpiva closed this as completed Jul 3, 2016
@maxpiva maxpiva reopened this Jul 3, 2016
@ElementalCrisis ElementalCrisis modified the milestone: Release 3.7 Sep 24, 2016
@ElementalCrisis ElementalCrisis added this to the Release 3.7 milestone Oct 6, 2016
@ElementalCrisis
Copy link
Member Author

Seems recent updates have fixed the speed problem, 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

4 participants