Alain Raap

Hi Son, we don’t use a clustered Moodle, files can best be stored on the application server itself with a fast storage, that gave us the best performance results.

Hi Ismail,

Did you have backup / restore problems before the upgrade? And do you use caching servers like Redis or Zend OpCache? Is your MariaDB database loaded in memory (InnoDB)?
That makes a big difference for performance issues.
NFS is also slow for a lot of I/O requests, we abandoned NFS already long time ago.

I followed the discussion about composer in Moodle 5.1, if you're running Moodle on a server without a connection to the internet, will this be a problem in the future? Will composer search for update packages outside the server environment? I miss the documentation about this feature that is new in Moodle 5.1

I found the problem, in the plugin auth_saml2 there is an attribute to change the userid to lowercase, my setting was an 'exact' match. After I changed this setting to 'lowercase', the error was solved and it worked like a charm.

Hi Emma,

In the database the username and email are stored correct, or do you mean the mapping in the settings of the plugin auth_saml2?