Other changes made:
I rely heavily on the Latex algebra filter, so I can't do that.
I'm not sure how that would decrease CPU time. Go on?
- Set the main navigation block to "show on course main page only." This was showing on all pages by default, so I was concerned that maybe the server had to work to rebuild this every time a student checked or submitted a question.
Where can I find this setting? That's probably smart. If PHP code is being excuted every time the page is loaded to generate this dynamic menu, that might help a bit.
- Changed setting on Server session handling. – Turned “Store session information in database” off.
Where can I find this setting? If the session is not being stored in the database, then less SQL is being executed, which means less CPU. I wonder what disadvantage this does. Is the session info stored completely in the browser's viewstate? It seems then you've saved SQL cycles, but then simply increased PHP cycles.
- Supplied the path to "du"
- Deleted many of the "blocks" I will never use.
reduces php cpu from rendering HTML. Could help.
- Edited the lib/accesslib.php to increase the context cache max size from 2500 to 5000.
How will this help? Esp with quizzes?
- I was not able to find the place to change the setting referred to on the moodle forum that read as follows:
- Edited lib/accesslib.php CONTEXT_CACHE_MAX_SIZE', 5000. (It used to be 2500)
I have no idea what this is about. What is the trade off?
- If there are performance problems loading course pages, check the Resource module settings. The setting resource_filterexternalpages is known to slow-down course pages and should be set to 'No' for better performance.
I would appreciate any feedback on the changes I have made as well as any other suggestions.
If you put all of the questions on one page, I think that would initially slam the server causing a massive CPU spike since PHP would have to generate thousands of lines of HTML at the same time.
You could tell your students to start the quiz in chunks of 5 students. Have one group start the quiz, then wait 10 seconds, have the next group start and wait 10 seconds, etc. Then you'd avoid the cpu spike.
What would be awesome is if moodle had a built in staggered quiz delay, so that it would prevent everyone from being able to start the quiz at the exact same time. You could set the quiz delay to 3 students, which means that only 3 students could start the quiz at the exact same time, with a delay of say 5 seconds. This has to be a great idea!