[mythtv-users] sluggish system, potential HD failure, and how best to get back up and runnin

Simon Hobson linux at thehobsons.co.uk
Tue Mar 4 19:05:48 UTC 2014

On 4 Mar 2014, at 16:47, Gabe Rubin <gaberubin at gmail.com> wrote:

> The key questions I have are, is a SSD a good option considering the DB gets many writess a day and I thought SSDs fail after a certain amount of writes.  Even if that is not an issue, is the cost worth it?  I don't neccesarily want to replace this drive with a HDD because I only need about 50-100 gigs for the system drive (maybe more, I am forgetting how large the db can get).

You can do a **LOT** to reduce the drive I/O load by tuning the DB. It also makes a vast difference to performance - reducing reschedule times (which happens any time a recording starts/ends or you add/change/delete a rule).

But in any case, SSDs include wear levelling algorithms so they don't keep writing to the same place all the time. The emptier the drive, the more (and more easily) it can spread the wear around. The DB doesn't get all that big anyway, my root system is only 1.2G used, and /var (which includes the database) has only 2G used - on a system that's recorded 7022 episodes of 670 shows over a little over 5 years.

I added an SSD not long ago (when eBuyer has a good deal on a 64G one). That and some DB tuning made a big difference to the system - reschedules normally happen before the "upcoming recordings" screen refreshes, while before, it would refresh and not show the last change (eg I could click "Don't record" and the program would still show as to be recorded until the next page refresh).

More information about the mythtv-users mailing list