Copy-pasting from an email I sent out:
... doing bulk actions on the Moodle instances can cause timeout failures if the action takes more than a minute or so to complete. So, actions should be done in small batches. For example,
1. Deleting users - first start with deleting one user, see how long it takes, and then scale to as many as possible to complete in one minute. A detailed post about automating this process is at
https://hnsws.blogspot.com/2024/10/moving-multiple-moodle-instances-from.html#deleting-users
2. Deleting courses - you may need to delete module by module, checking how long each process takes, as above.
3. Running ad-hoc queries - please filter for small result sets and optimize code so that the query completes within a minute or two.
Similarly, when designing the course pages, please use themes / modules / etc in such a way that only a limited number of images and or other content loads on a single page - otherwise, the site will be experienced as slow to load, slow to edit, etc. A rule of thumb would be to limit the scrolling to two screen heights, and not more than that.
In general, if you experience timeout errors (which usually will be displayed as "gateway error" if using cloudflare), you can simply close and re-open your browser after a couple of minutes, login again, and the site should load.
No comments:
Post a Comment