Talk:Performance 2.x

Sessions not in database

(Here's a section which I would suggest should be considered for possible inclusion on the page, after whatever modifications are needed. This was reported by our systems team as the most critical performance problem currently identified in Moodle 2.)

Database sessions cause a performance problem because they increase load on the one resource (the database) which is, in most situations, hardest to scale.

(I.e. increasing load on the web server slower is fine, we can add another one. Increased load on the database is much harder to handle.)

Moodle 1.9 supported other types of session which are significantly preferable for performance reasons.

Unfortunately there are some parts of the system which only work with database sessions. For example, some auth plugins can only work with database sessions. There may be other parts of code which also somewhat depend on database sessions for fully correct operation so this could be a complicated problem to fix, but I think it's still a serious problem.

At the OU we have implemented memcache sessions in order to resolve this problem.

Sam marshall 23:53, 24 May 2011 (WST)