Difference between revisions of "Troubleshooting:Mythfilldatabase IO bottleneck"

From MythTV Official Wiki
Jump to: navigation, search
(Migrate MySQL)
(Add "Outdated" tag)
Line 1: Line 1:
=The Issue=
=The Issue=

Latest revision as of 16:21, 21 August 2016

Time.png Outdated: The information on this page may no longer be relevant to the current release of MythTV, 31.0. Please consider helping to update it.

The Issue

When updating a significant number of channels mythfilldatabase and MySQL can cause enough disk or I/O activity to interfere with recordings, playback, and live tv. This interference can cause recordings or playback to become garbled, and may even cause the backend to cancel the recording or stop entirely. It is also possible for MySQL to saturate the ATA bus, not simply the hard disk.


There are two known resolutions to this problem. You can choose to either reduce the number of channels you subscribe to, or you can migrate your MySQL database to another machine or hard disk.

a 3rd option would be to reduce the cpu usage of the process using cpulimit - of course that it will take a longer time to complete but...

Reduce Channel Listings

By far, the simplest method of resolving the issue is to reduce the number of channels mythfilldatabase updates. If you are using Schedules Direct you can manage this from the subscription site. I do not have any experience with XMLTV, but you will probably need to check both your configuration and service provider to reduce the updated channels.

Migrate MySQL

If you must keep all of those channels, the recommended solution is to move your MySQL database to a separate hard disk. In fact it is normally suggested that you use a seperate dedicated hard drive for your media from the beginning, keeping your root, var and home partitions on different disk. You will probably want to install the database hard disk on a different bus if using PATA. This allows MySQL to saturate the database bus without interfering with the bus your media drive is connected to.

Alternatively, one extreme solution might be to consider running MySQL on another server. You can move the mythconverg database by backing up from your current server, and restoring on the new one. This is not recommended and may not be possible with future versions of MythTV.

Changing the structure of your linux installation is distribution dependent. However, the MySQL files can be copied and moved so long as mysqld is not running. Check your linux distribution for more information.