Moodle Pages Slow to Load / Respond. Moodle performance issu

We have three issues that I think are related.

1. When setting up new menu items, the process fails with SQL error. See screen shots. Every so ften the process will succeed. At the moment I can not create a new menue item.
2. Access Joomdle pages often fails in a similar way. This is much less often and feels like it's a first thing in the morning thing.
3. Joomdle pages are always slow to render.

Joomdle Sys tools passed.

I just reinstalled Joomdle to see if that would help but no.

Moodle 2.x Joomla 1.5.2

By the way I found this in the /administrator/error_log...

[30-Mar-2011 13:03:14] PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'plug_joomdlehookscb_uninstall' not found or invalid function name in /home/clique/public_html/administrator/components/com_comprofiler/library/cb/cb.installer.php on line 1254

Hi Brian.

I have only seen similar sql errors trying to install on a low-memory server.

Does the error only happen with joomdle menu items? All items?
When did error started to appear?

At the moment we think this is a Moodle DB performance issue. I'll let you know what we find.

I'm having the same issue. At times nothing opens and it times out. Other times it works fine. Sometimes a page will simply say it cannot be found and then you click again and its there. What is the minimum memory recommended? Can this work on a shared server?

Turns out our problem was related to a Moodle cache setting. Admin ---> Themes --> Theme settings --> Theme designer mode was set to yes. Pretty stupid really.

Not a complete loss of time though. Some of the performance tweaks we tested did help. Apache MemCache gave a notable boost.

This is the one of the error messages I get

Error: Database connection failed
It is possible that the database is overloaded or otherwise not running properly.
The site administrator should also check that the database details have been correctly specified in config.php
Warning: mysqli::close() [mysqli.close]: Couldn't fetch mysqli in /home/cosmic14/public_html/classes/lib/dml/mysqli_native_moodle_database.php on line 336

Might be the same type of error. The cache configuration problem was slowing everything else down to the point were we were getting DB time out issues. We are not using mysqli so it could be something else completely.

It's defiantly a Moodle issue though, not Joomdle.

I checked that cache setting and it was already turned off. I do think it is a Moodle 2.0.2 issue - I was over on the Moodle forums and more people than I were noting how slow it is, even in comparison with 2.0.1.

@bscunningham

Thanks for your solution and feedback on this. Personally, I have not moved to Moodle 2 and am a little worried now


I will keep this thread open in case there is anything other information that can help out even though it's not Joomdle related.