Library Database File Size after Sonic Analysis

Plex Media Server Metadata & Adding Files
,
1

Hello everyone,

I enabled sonic analysis on my music library (64000 tracks) a couple of months ago and I just realised (after a failed timed-out backup) that my com.plexapp.plugins.library.db file is sitting at around 70GB. Is that normal? Should I run the DBRepair script (GitHub - ChuckPa/DBRepair: Database repair utility for Plex Media Server databases) and if yes by choosing which options?

I remember that when I created my music library in Plex I regretted the way it has been set up and I deleted it and created a new one. Plex is notorious for not cleaning up after itself so maybe the com.plexapp.plugins.library.db contains garbage from previous libraries too.

All I worry is that the file might get so big that plex will not be able to read from it and I will loose my library (and its years long history).

Thanks so much for your feedback!

2

My library db is only about 2.5gb and I have a music library with 135k tracks.

Did you by chance install a beta recently that had a terrible bug that exploded DB sizes? It’s fixed now but the large DB remains.

3

No betas, I am in the latest channel of linuxserver distro. Do you have 135K tracks with sonic analysis on?

5

Sonic Analysis has probably nothing to do with the issue.
You are most likely affected by this Library.db size more than doubled in latest version

The automatic solution will arrive when the server version 1.42.8 goes into the public channel.
If you need to solve it now, because your server is unbearably slow or almost doesn’t work at all, there are several methods described in the thread to repair it with a few SQL commands.

6

Yes the RepairDB did very little It went from 69GB to 65GB. I am currently on Version 1.41.8.9834 I will wait for 1.42.8 when it comes out. Thanks.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.