@ChuckPa is talking about “There were those users who experienced a ballooning effect. The database grew in size from 200 MB → 3 GB for no reason.”
And that it should be fixed now, has anyone experienced this?
There was also talk about the Plex Team working on a fix for already big databases.
About removing the Junk that was already in them.
Some of my database files are still very large, over 1gb some almost 2gb.
Was wondering if there was anything that could be done with this.
Or that maybe i should remake my server?
If you are haunted by the ballooning error we found, then PMS has a fix for it, and will gradually during the night scheduled jobs cut slices of you database, until all the faulty records are gone.
You should be able to see this simply by comparing the size of your current database with the size of the scheduled backup files
And if you can’t, then you might have another issue, and I can then only recommend, that you power off PMS, zip the databases, and upload to like dropbox.
Then DM me the download link, and I’ll take a look
Now you mention it i do see a slight decrease in size over the backup files.
The blobs.db wen from 2022-04-28 1.92gb, to the last backup 22-05-10 being 1.75gb.
Will it get smaller in size even?
Will this also help prevent the Sqlite3 sleeping 200ms error?
Also, i got about 40k items in my libraries. What size should i expect the databases to become aprox?