On 17/10/05, Andrew Wilson <[EMAIL PROTECTED]> wrote: > My mythconverg database is now about 35MB, and I'm starting ot look at > embedded devices to host it, so it would be nice to have the DB > smaller if possible.
Less recordings = smaller DB ;-) > Not knowing much about SQL, I did this to figure out which tables are > eating all that space: > > mysqldump mythconverg | grep -n "^-- Dumping" > /tmp/db > > That spews out the line numbers in the dump for the start of each > table. recordedmarkup accounted for 92% of the lines in my database. > Surely some mistake??? Nope > I'm only vaguely aware of what this table is for ... commercial > cutlist? - which I don't use anyway. AFAIK it contains to offsets in the recordingsfile to the different types of frames etc... You need when seeking through a recording (ffwd, rew, skip etc...). If this table is corrupt or empty, you'll notice strange behaviour during playback, e.g. the frontend won't know how long the recording is. > - What's going on? What's the table for, and why is it so big? > - Can I empty this table in my db? I tried it and the database dump > went from 36MB to 6MB, though I've not played with the frontend to see > what damage I caused. mysqld memory usage in top also reduced > significantly (which was the point of the exercise) > - Is there a bug where old markup is not removed from the table, or > excessive markup entries are being produced? > > cheers > Andrew > _______________________________________________ > mythtv-users mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
