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

Bad performance in large courses #95

Open
Dmfama20 opened this issue Oct 7, 2022 · 2 comments
Open

Bad performance in large courses #95

Dmfama20 opened this issue Oct 7, 2022 · 2 comments
Labels
known issue A known limitation unlikely to be solved except by significant redesign

Comments

@Dmfama20
Copy link

Dmfama20 commented Oct 7, 2022

Hi,
we're using this block in a university course with approx. 350 participants and 130 activities. Unfortunately, we observed really bad performance when using the "overview participants" mode in combination with showing all participants (in order to get an overview of the progress of the whole course).
Here is a report of the performance:

Overall Summary   /blocks/completion_progress/overview.php
Total Incl. Wall Time (microsec): 332,423,108 microsecs
Total Incl. CPU (microsecs): 138,720,026 microsecs
Total Incl. MemUse (bytes): 32,169,256 bytes
Total Incl. PeakMemUse (bytes): 73,938,344 bytes
Number of Function Calls: 134,399,103

In my opinion the reasons of the bad performance are the huge amount of sql queries consuming lots of memory.
Do you ever thought about an optimization of code in view of performance?

TIA!
Alex

@jonof
Copy link
Owner

jonof commented Oct 17, 2022

It's always going to be monstrous when you're sorting by completion percentage, especially in courses with lots of participants and activities.

@jonof jonof added the known issue A known limitation unlikely to be solved except by significant redesign label Nov 2, 2023
@izendegi
Copy link

We also experienced this kind of performance issues.

It seems like the query is executed for all users even if they are separated on several pages, could it be improved limiting the query somehow to limit it to those users shown on the current page?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
known issue A known limitation unlikely to be solved except by significant redesign
Projects
None yet
Development

No branches or pull requests

3 participants