Usability problems with many gym members #144
Milestone
Comments
|
Current status: with 1000 users the gym overview fires around 4000 database queries and takes around a minute to render |
rolandgeider
added a commit
that referenced
this issue
Oct 3, 2015
By filtering with queries the user's permissions, this reduces the number of SQL queries for the overview by roughly 50%. While this is not bad, calculating the last activity is still very expensive and must be further optimized. See #144
rolandgeider
added a commit
that referenced
this issue
Oct 25, 2015
While this further reduces the number of queries in the user overview by around a third, it is not enough. It will probably be necessary to save this to a cache table and keep the values updated via signals. See #144
rolandgeider
added a commit
that referenced
this issue
Oct 25, 2015
This table can store expensive queries, etc. such as the last activity. With this, the gym user overview can load all the user data (including the last activity) with only one query. Fixes #144
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current implementation of gym members has problems when the gym has a large amount of members. This should be perhaps moved to a dedicated page for members, pagination and some kind of search are probably needed here.
The dummy data generator in extras can be used to generate the test users.
The text was updated successfully, but these errors were encountered: