[mythtv-users] Converting from DD to xmltv

Gary Buhrmaster gary.buhrmaster at gmail.com
Sun Nov 11 16:24:36 UTC 2018


On Sun, Nov 11, 2018 at 1:26 PM Richard Shaw <hobbes1069 at gmail.com> wrote:

> Is there any downside to running --no-allatonce?

Some additional overhead of invoking the grabbers
repeatedly and processing some duplicate information,
although due to caching the overheads in the grabbers
themselves is not horrendous (at least for the SD grabbers,
some other grabbers have much higher overheads when).

As I recall you typically also want to specify "--refresh all"
since the default will only refresh some specific days.

And if you are one of those with an interesting set
of xmltvids (for example, translators with different
xmltvids even though they are the same station)
you may get repeated messages regarding (lack of)
matching for those stations.

None of those are known show stoppers, and if you
have a backend with more limited memory the
end result of avoiding swapping is probably better.

> I'm pretty much running stock MariaDB from Fedora with some tuning as recommended from mysqltuner.

mythfilldatabase performs a fair number of updates
(for some good, bad, and ugly reasons), which
depending on your database settings, and disks
(especially older/slower real HDDs) can simply take
time to complete.

>  so for now moving the run time to a time I don't really care or record anything may be the best "solution".

It should be noted that unlike the DD source,
the JSON source is updated up to 4 times
a day, so if there are late breaking schedule
changes (and it makes it through the various
network, upstream guide provider, and Schedules
Direct (which is not at all assured)) you can get
more accurate data by running mythfilldatabase
a few times a day.


More information about the mythtv-users mailing list