We've recently made an upgrade to 1.9.6+, after our 1.8.3 installation had a corruption in one of the tables that was hard to recover from. So, we decided to restore the backup and migrate to 1.9.6+ as well.
The upgrade was actually two-step: first we went to 1.8.10+ and then to 1.9.6+. It was all flawless - no error messages or even warnings.
Unfortunately we're suffering a lot of performance problems - several php scripts are suddenly eating up CPU like crazy. So much that we start getting Internal Server Errors or simply some pages just dont load anymore (such as listing forum posts for a particular user).
After investigating in the forums, the hint was to check out the mysql-slow.log file. It is attached here, but I still cant believe that our 1.3 GB database is causing all that slowdown. The biggest table is mdl_log, which is now ~560MB (after shrinking it frorm 1.2GB). The rest is about some KBs ou MBs. I have been through the following checklist:
- Cache use: we set to internal by now. Cant see much difference, to be honest. Still getting those pesky Internal Server Errors.
- Check if there's any index missing: using XMLDB experimental, it checked all tables and the result is that all tables are indexed. No index missing.
Yet, the attached Runtime Status file from phpMyadmin clearly states that JOINs are not using the indexes properly. I'm not sure if this is related to missing indexes after the upgrade.
In addition, our mysql-slow.log is at http://18.104.22.168/moodle/mysql-slow.log
Our server configuration:
Processor #1 Vendor: GenuineIntel Processor #1 Name: Intel(R) Pentium(R) 4 CPU 3.20GHz Processor #1 speed: 3207.411 MHz Processor #1 cache size: 2048 KB Processor #2 Vendor: GenuineIntel Processor #2 Name: Intel(R) Pentium(R) 4 CPU 3.20GHz Processor #2 speed: 3207.411 MHz Processor #2 cache size: 2048 KB - 2 GB of RAM - 170GB SCSI Hardisk We're running Apache2, MySQL 5, PHP 4 and Exim on this server. Can anyone give us a hint on how to proceed on this? We've tried a number of minor tweaks, such as disabling Online Users Module, but with no success. regards, - Breno Jacinto