[mythtv-users] mysql 100% cpu since upgrading to fedora 22 and mythtv-0.27.4 from git

[Udo van den Heuvel]

Hello,

How can I find out why mysqld (mariadb) is eating so much cpu ever since
upgrading to Fedora 22 and MythTV 0.27.4?

# mysqladmin processlist -v
+----+--------+-----------+-------------+---------+------+-------+-----------------------+----------+
| Id | User   | Host      | db          | Command | Time | State | Info
                 | Progress |
+----+--------+-----------+-------------+---------+------+-------+-----------------------+----------+
| 2  | mythtv | localhost | mythconverg | Sleep   | 58   |       |
                 | 0.000    |
| 4  | mythtv | localhost | mythconverg | Sleep   | 70   |       |
                 | 0.000    |
| 5  | mythtv | localhost | mythconverg | Sleep   | 70   |       |
                 | 0.000    |
| 6  | mythtv | localhost | mythconverg | Sleep   | 2    |       |
                 | 0.000    |
| 7  | mythtv | localhost | mythconverg | Sleep   | 34   |       |
                 | 0.000    |
| 25 | mythtv | localhost | mythconverg | Sleep   | 4327 |       |
                 | 0.000    |
| 26 | mythtv | localhost | mythconverg | Sleep   | 4    |       |
                 | 0.000    |
| 28 | mythtv | localhost | mythconverg | Sleep   | 310  |       |
                 | 0.000    |
| 30 | mythtv | localhost | mythconverg | Sleep   | 70   |       |
                 | 0.000    |
| 31 | mythtv | localhost | mythconverg | Sleep   | 58   |       |
                 | 0.000    |
| 32 | mythtv | localhost | mythconverg | Sleep   | 69   |       |
                 | 0.000    |
| 36 | mythtv | localhost | mythconverg | Sleep   | 63   |       |
                 | 0.000    |
| 57 | mythtv | localhost | mythconverg | Sleep   | 2889 |       |
                 | 0.000    |
| 62 | mythtv | localhost | mythconverg | Sleep   | 0    |       |
                 | 0.000    |
| 90 | root   | localhost |             | Query   | 0    | init  | show
full processlist | 0.000    |
+----+--------+-----------+-------------+---------+------+-------+-----------------------+----------+

What is actually happening?
My SQL-limiting Power Search recording schedules are still there.
Yet still I see this behaviour.

Any ideas?

Kind regards,
Udo