Our university has a Moodle 3.2.5 installation with MSSQL as a DB (our only choice).
We have currently 60 000 registered users and a daily average of 2500 concurrent ones.
We have on premise hosting at the campus with:
- VMWare virtual host with Red Hat 7.5
- Prozessors 8
- Memory 8GB
- Disk Space 64GB - application
- Apache version is 2.4.27
- PHP version 7.1.8
- Microsoft SQL Server 2016 with 20GB RAM
Because of the number of cohorts and completions the system is having a bad time with the performance. Especially the scheduled tasks take a lot of time to complete. Another example is loading of the user list - it takes about 6 seconds to load the page.
The system architecture is pretty monolithic. We are expecting the system to get another 50 000 users from another university and online programs. So at the end we will end with >100 000 users.
Our target would be to setup everything in two phases:
- Stabilization: It seems, that the base of the hosting architecture is not enough for the current users. What would be the first step from your point of view? (I alredy read https://moodle.org/mod/forum/discuss.php?d=161040, but it confuses me a bit)
- Further development of the solution: Is there a way to make everything more scalable? Or best practices for doing it, as there is a ton of info in the web, but everything is different.
Our first suggestion was a partner, but sadly we must do it with internal forces, because of the lack of budget. So any feedback will be helpfull.