[mythtv] Video playback framerate
Stephen Worthington
stephen_agent at jsw.gen.nz
Tue Jan 8 15:34:59 UTC 2019
On Tue, 8 Jan 2019 10:33:29 +0000, you wrote:
>On 8 January 2019 1:28:41 pm Stephen Worthington <stephen_agent at jsw.gen.nz>
>wrote:
>
>> On Mon, 7 Jan 2019 14:25:11 +0000, you wrote:
>>
>>> How big are peoples databases currently running...
>>
>> I have a monster database. So increasing the size of the recordedseek
>> table would have a big impact on me:
>>
>> root at mypvr:/var/lib/mysql# du -h mythconverg
>> 14G mythconverg
>
>14G, of which 13.4G is recordedseek table alone.
>
>
>> 4.0K mythconverg/recordedseek.frm
>> 7.0G mythconverg/recordedseek.MYD
>> 6.4G mythconverg/recordedseek.MYI
Yes, that is the way it works. In most databases, most of the storage
is used in the recordedseek table. I should also say that I am not
opposed to changes to recordedseek - it is one of the good things
about MythTV as it makes skipping about in recordings work
excellently, and improving that is a good thing. I just want everyone
to be aware of the potential for problems with databases as large as
mine. Imagine how long a schema update might take if all of my
recordedseek had to be converted to a new format. And it would be
dramatically worse if all of my recordings needed to be rescanned to
do it - how long would it take to just read 65 Tbytes of data, let
alone do processing on it?
More information about the mythtv-dev
mailing list