Database file size

[jeauxbleaux]

Wow! I just looked at my database and was chagrined to see that it is just under 2G for about 600 movies and 4000 songs.

I suspect that there is a balance to be struck here. Making the database fully relational will dramatically reduce its size, but may reduce performance in some cases, like multiple users browsing menus on endpoint devices. Replication may shorten menu response time but balloons the database size, especially with all the duplicated bitmaps. It also slows down the Mezzmo application; adding files and editing entries can sometimes be a frustratingly slow process.

All that said, I think there has got to be a way to eliminate most if not all of this replicated data, particularly the thumbnails, without an excessive performance hit. At least now I know why my Mezzmo application runs so much slower than it used to. I know for a fact that MEZZMO.DB was about 65Mb with v2.x.

Please add my voice to the chorus to clean this up. Thanks.

[Paul]

Thanks for the feedback.

[JMC]

My DB is 7GB - and database maintenance in the new verions didn't help shrinking that. Would adrian please publish the script or you guys please fix this? The DB growed more than 5GB in the last 2 versions...

[Paul]

We're looking into this for the next major version of Mezzmo.

[Lifferds]

Mine is 406 mB but I found the MezzmoTranscode.db was 97 mB with only a single entry, even after compacting. I ran vacuum on it in SQLLite and it shrank to 15 kB. Looks like the compact feature does not compact all db's.

[JMC]

Holy crap... As mentioned in another thread regarding the permanent task changing playlists... I just opened the database with a SQLite browser - MGOPlaylist has 102341 elements in my database. From the HUGE number of thumbnails inside the database (108533!): Am I right, that for a TV Show for example every episode gets an own thumbnail of the same picture used for the whole show? Now wonder this database is growing all over again...

Edit:
Deleting the dynamic video playlists for file type, actor and director followed by a compact compacted it from more than 7GB to 3,4GB. Compacted it before this to make sure it's the playlists... So you are telling me more more than 3GB inside the database is because of the dynamic playlists????

[Paul]

The storing of artwork is not optimal at the moment, and this will be fixed for the next version.