Database Observations after 1.40.0.7775 Migration

General Discussions
1

Below are some observations, I have noticed over the past day or so after upgrade to 1.40.0.7775 which contains a database migration change:

  1. before upgrade my main db was 805MB
  2. after upgrade, migration and optimize of dbs my main db was 1008MB
  3. after running DBRepair.sh with stop automatic status start exit options the db came down to 930MB
2023-12-21 08.37.04 - Repair  - Verify main database - PASS (Size: 1024MB/930MB).
2023-12-21 08.37.05 - Repair  - Verify blobs database - PASS (Size: 405MB/473MB).

I’ve also noticed optimize of the db takes a fair bit longer to now complete, taking approx 40-50 seconds now whereas before it was around 15-20.

BTW… I’m not saying any of this is a problem, its just observations and could be useful as a reference for others.

For context my system is running dedicated hw with ubuntu 23:10. I’ve 4100+ movies, 37,000+ episodes, 112,000 tracks and 67,000+ dashboard history entries. I don’t use intro, credit, video preview or chapter markers and also don’t use sonic but do have loudness.

2

This is expected for now.

As described in my post here: 1.40.0.7775 Database Changes? - #2 by drzoidberg33 we’ve changed the structure for one of the database columns.

In order to allow PMS to downgrade to earlier versions we need to essentially keep a copy of the data in that column in the old format which is basically doubling the size of the data in the column.

We will remove the duplicate data when there is a clear downgrade path.