idimager.thumbs.db - 40 GB size?

[Frankyls]

Hi,
I'm actually testing PSU V2 versus IDI 5 and realized that the file idimager.thumbs.db generated by PSU V2 is much bigger than the one IDI 5 generated:
PSU: 40,6 GB
IDI5: 3,4 GB

I didn't expect such a big difference. Also I do not want to have such a big file located on my SSD (even if a fast SSD might be the best place for a database file).
I already compressed the DB, but that only saved 0,3 GB.
Is that normal?

regards

Frank

[gcoupe]

I think you can select the size of your thumb previews - which has an impact on the size of the thumbs database.

However, the main point is that you can move the thumbs database off your SSD. I had a similar issue, which Hert addressed. See http://forum.idimager.com/viewtopic.php?f=57&t=23082

[Frankyls]

Thanks for your quick answer. I moved the DB already sucessfully. Next step is to find the switch to reduce the thumbnail size. I hope I can reduce it without reimporting all

[gcoupe]

It's in the Catalog Settings section of the Preferences...

[Frankyls]

Thank you very much, I got it now. I'll post the result hopefully soon.

[Hert]

After reducing the size of the previews and then rebuilding the thumbs/previews then don't forget to compact the database

[fbungarz]

Hi all,
with version 2 of PSU out and so many great improvements I am finally also considering the move, but database size does worry me quite a bit as well.

I have been following this discussion about file size of the thumbs database for a while and before actually migrating would like some 'rules of thumb' how big the thumbs database gets according to which thumb size setting.
If I select the same thumb size in PSU as in IDI, do I get approximately the same database size or doe it get a lot bigger?

One huge advantage of using IDI is offline mode, while not connected to my images I can still browse, tag, etc. Now, if I am using a laptop with a small SDD and have to move the thumbs database off the SDD I then have to carry around that drive and have it connected, else cannot use offline mode, right? Because then not just the images, but also the thumbs of the database are offline too, right? To me that defies the purpose of having an offline mode...

Can anyone share how different thumbnail settings will affect database size?

Also, could someone clarify the different sizes? In PSU 640 px is the lowest available setting, 1680 the highest (apparently no custom size setting, why not?). In IDI there is small (140), Normal (160), large (180), very large (220) and custom. I assume in both cases this refers to longest side in pixels of the thumbs, or does it refer to the previews?

In IDI I am currently using normal (160). Such a low setting is not available in PSU, where the lowest number is 640, i.e., four times as big as my current IDI setting. My current IDI database is 5.7 GB, does that mean migrating to PSU my database will be four times larger, 22.8 GB ???

There is definitely NO way I would ever want to have a 20 GB database file on my SDD, where I have just 40 GB free left. Currently I am switching back and forth between desktop and laptop using SyncBack to keep databases on both up-to-date. I would be really concerned having to regularly replace a 20 GB file on my SDD. That would result in a lot of writing of huge amounts of data to that drive, which is not at all sustainable, causing a lot of wear to that drive. And even if that was not an issue, using SyncBack to synchronize PC and Laptop already with a 5.7 GB file takes about 10 minutes and with 20 GB then 4 times as long? 40 minutes just to move my desktop database to the laptop to take it on the road???

Any suggestions?

Thanks,
Frank

[Hert]

In PSU 640 px is the lowest available setting, 1680 the highest (apparently no custom size setting, why not?). In IDI there is small (140), Normal (160), large (180), very large (220) and custom. I assume in both cases this refers to longest side in pixels of the thumbs, or does it refer to the previews?

If you want the smallest preview database possible then set a preview size of 640px. We can talk about it but that won't make it any smaller.
Hert

[Frankyls]

I'm just testing it on my laptop, both IDI and PSU thumb size set to 640 px. Unfortunatly the process is still running, despite only having 1/10 of my photos on the laptop. I'll report the file size.
The 40 GB on my desktop is with a thumb size of 1680 !

Result:
On my laptop idimager.thumbs.db size was 15,4 GB. Setting thumbnail size from 1680 to 640 px and then compressing both databases didn't change the size of idimager.thumbs.db file, it is still 14,5 GB (a bug or I missed something or did something wrong).
Will continue tomorrow.

[Frankyls]

After reducing the size of the previews and then rebuilding the thumbs/previews then don't forget to compact the database

Ok, I think here is the point I missed - the rebuilding of thumbs/previews
Unfortunately I can't identify a menu point which will do this rebuilding (I use PSU with German language)

[weidmic]

You should not migrate your IDimager thumbs database to PSU; It's better to let PSU create a new one...
Then use build missing Thumbnails and Previews from the tools menu

[weidmic]

Werkzeuge - Fehlende Miniaturansichten und Voransichten erzeugen

[fbungarz]

We can talk about it but that won't make it any smaller.

So, you are saying: simply bad luck if you happen to have one of those new laptops with a small SDDs ?

[fbungarz]

And BTW, perhaps consider updating your website:

Always take your images with you... even if your images are physically inaccessible, they travel with you. Switch the application to TRAVEL mode and Photo Supreme remains fully functional.

Say, you have a MAcBook Air a Samsung Series 9 or many other new laptops with a relatively small 128 GB SDD. And then a 40 GB thumbs database? That is about a third of the whole SDD ONLY for the tumbs database !

[tomas]

I too was dismayed at the size of the thumbs DB.
So I just went thru the process described here of: reducing the preview size from the default to 720, rebuilding thumbs, compacting DB.
My thumbs.db INCREASED in size. So much for that idea.