[mythtv-users] database size
Michael T. Dean
mtdean at thirdcontact.com
Wed Apr 2 02:36:34 UTC 2008
On 04/01/2008 10:14 PM, Frank Lynch wrote:
> On Tue, Apr 1, 2008 at 10:05 PM, Michael T. Dean wrote:
>> On 04/01/2008 09:53 PM, Frank Lynch wrote:
>>> I've been running mythtv happily for a couple of years, tonight I
>>> decided to upgrade to 0.21 & migrate from Fedora Core 4 to ubuntu
>>> gutsy. All appears to be going well at the moment.
>>> However during the process I backedup my db & noticed that its a
>>> whopping 2.2GB!
>> By what measure? Looking at the binary files? Looking at the size of
>> the backup? Basically, it sounds large, but I want to verify that
>> you're using some appropriate means of measuring the size.
> the 2.2GB file is the output from mysqldump for mythconverg before I gzip'd
> it. It compresses down to ~200 mb.
Better would be a long listing of the MySQL data directory. I'd
actually be interested in seeing one (perhaps today--while large, and
tomorrow--which could be much smaller). Something like:
ls -lS /var/lib/mysql/mythconverg
ls -lS /srv/mysql/mythconverg
depending on where your distro puts the DB data. Since there are so
many tables, feel free to bzip2 the output (or, if it's just a few
tables at the top, you can chop it with " | head -n 30" or something).
The only table that should be very large is recordedseek, as it contains
a couple of records per second of recorded video (and, if using
mythcommflag --video, per MythVideo video). So, extrapolating from my
65MB data/60MB index of recordedseek for 348 hours of recorded TV taking
up >1.8TiB of storage (and considering all other data would be
negligible), to really have a multi-gigabyte DB, you'd need to have A
Whole Lot (sorry about the technical terms) of recorded video.
More information about the mythtv-users