Hooray! Another thing should also be addressed is the number of rows in table TimerScheduledJobs and TimerRunningJobs, in some extreme cases they can be huge too.
For instance, in one SP2013 farm we have 3000+ site collections and RecordPoint creates 3 timer jobs for each site collection, two of these timer jobs are scheduled to run every minute. It has a huge impact on the farm performance and also cause large SQL transaction logs piling up.