Thought I'd share this with the forum as someone else might have the same problem. We had CPU maxed out on our livecycle server a while ago. Traced it to MySQL and a query that livecycle was running that involved a complete table scan.
mysql> use adobe;
mysql> ALTER TABLE EDCREVOKATIONENTITY ADD index EDCREVOKATIONENTITY$ix$updatedate ( updatedate );
Query OK, 267851 rows affected (15 min 32.22 sec)
Records: 267851 Duplicates: 0 Warnings: 0
Adding this index fixed the problem straight away.