We've been running Moodle 2.9 (started with 2.6) for quite some time now as a hosting platform for SCORM packages only, this has worked quite well so far but I'm looking for some advise on how to deal with the enormous table that we seem to got stuck with.
So far we have over 8500 users registered on the site, it's hosted in a clustered environment and performance is fine after tweaking the servers a little. Because we made use of SCORM only we're now stuck with the table scorm_scoes_track having over 64.000.000 records.
Now that in itself is not the biggest problem, but every time we want to update an activity it takes between 6 to up to 20 minutes for the page load to be done, because Moodle starts recalculating the scores in the gradebook. Which seems logical, however the activities we're uploading are simply restyled and do not make an alteration to the score system in any way.
With over 500 activities to update we're looking at making a repository and linking the files from there, this works fine in our test environment, but now that we're looking to implement this on the live server we're looking at more then a week's worth of re-linking files because it takes so long for the process to complete.
Could anyone advise me on what a good way would be to reduce this? We tried locking the gradebook to see if that would speed up the process, but there doesn't seem to be any difference. Any help at all would be appreciated, because the live site is being used daily by paying customers and it's not really an option to put it offline for more then a day or so.