[tars]

If you remove items from the database (because you remove about 1/2 of the actors), the database _should_ shrink after compacting. I say _should_ here, because that are internals of the mvstore of the H2 database (we use that database engine, we did not write our own).

just read a bit in the source of the MVStore and I saw, that this has a versioning feature -> per default 5 versions of one object (movie) are kept in the database. Since I was not aware of this parameter, the default of 5 versions is active within tmm (although we do not make use of it). I will try to remove that

 

I found out that this parameter is only used in in-memory-databases and thus does not apply to our use case.

I will observe this issue and make some tests with newer versions of the mvstore in the next weeks

Yesterday I changed datasource for about 5% of my movie collection, and it ended up increasing the db size by 46%.
I haven't tried yet but I'm pretty sure if I re-create the library I will get the original smaller db size again.
Looks like the db is designed to keep old data as the name MVstore standing for multi-version store.

See some discussions about its size issue:
https://github.com/h2database/h2database/issues/301
https://github.com/h2database/h2database/issues/1820