You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did some research on loading times for the meeting plugin and found out that the calculation for getIconNavigation() is quite slow. Main Problem is the fetching of all meetings for a specific course from the database in MeetingCourse::findActiveByCourseId().
First of all, the query is pretty slow since it has to sort a an unindexed column --> maybe an index for vc_meetings.name should be added and the ORDER BY m.name + 0, m.name should be changed to ORDER BY m.name for a faster sorting.
Second, even if the query is optimised, it takes ~0.015 seconds to execute on our systems (the table is quite large with 34k entries). Having e.g. 8 different courses in the course overview adds up to 100ms waiting time just for these queries, and most students have way more than 8 courses in the list. What to do? Maybe implement a cache:
Hi @schuettloeffel-elsa
Thanks for your contribution.
Just for your info: You could have made a PR for this enhancement.
The part for optimizing the query for sorting, I would prefer not to change it for now.
I did some research on loading times for the meeting plugin and found out that the calculation for getIconNavigation() is quite slow. Main Problem is the fetching of all meetings for a specific course from the database in MeetingCourse::findActiveByCourseId().
First of all, the query is pretty slow since it has to sort a an unindexed column --> maybe an index for vc_meetings.name should be added and the
ORDER BY m.name + 0, m.name
should be changed toORDER BY m.name
for a faster sorting.Second, even if the query is optimised, it takes ~0.015 seconds to execute on our systems (the table is quite large with 34k entries). Having e.g. 8 different courses in the course overview adds up to 100ms waiting time just for these queries, and most students have way more than 8 courses in the list. What to do? Maybe implement a cache:
--> having that cache improved the response time for the course overview by 100ms (from 230ms to 130ms) on our test systems!
The text was updated successfully, but these errors were encountered: