[Digikam-users] Long database sync
Johannes Kapune
listen at kapune.de
Sun May 10 22:56:14 BST 2015
Hi Joram,
normally DigiKam uses SQLite, what's a database one file basis.
Each change has to be written directly to prevent data loss.
(and sometimes to read this databasefile back after each change) If you
have to do a lot of changes it can take a lot of time.
If you start this sync you have to wait until it comes to an end.
In later use there is normally only a few changes and for this this type
of database works well.
Johannes
Am 09.05.2015 um 20:51 schrieb Noeck:
> Hi,
>
> I did Extras > Management⊠(Extras > Wartung⊠in German) in my digikam
> 4.9 installation from the ppa. And then I did a database sync from the
> files to the database.
>
> It takes hours (after 4h it currently reached 14%) and it shows a high
> disk write rate: 14MB/s. Why does it write so much and where? The
> database size does not change much (in those 4 hours it has grown by
> 1MB) and the image files do not seem to be touched (as expected when
> doing a sync files->database). If it just changes the database contents
> with 14MB/s, couldn't it do that in memory and then dump the result into
> the file only once?
>
> So where does it write to with 14MB/s?
>
> Thanks for clarification,
> Joram
>
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users
>
More information about the Digikam-users
mailing list