https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #14 from Simon <freisi...@gmail.com> --- Indeed, my setup is far from optimal for disk io. I have both the database and the images on a ntfs pratition of a hard disk on my laptop (at least not system hd). I thought that the database would be automatically cached in ram. I will look at it again some time. Thanks again for your help. On 02/05/16 21:14, Maik Qualmann via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=362023 > > --- Comment #13 from Maik Qualmann <metzping...@gmail.com> --- > This is are long waiting times, up to 5 seconds until a scan is completed for > one image. Disabling the scanning does not help, he would be rescheduled in > any > case. Modification date or file size have changed and need to be updated in > the > DB. Writing to the SQLite DB is the time problem. The SQLite DB to put on an > SSD drive is strongly recommended. Here are a few measured values, writing of > one image information in the DB this include read new information from image > (images on HDD - EXT4): > > HDD: > SQLite: 180-270ms > internal MySQL: 40-70ms > > SSD: > SQLite: 30-60ms > > Are the images on an NTFS partition? Is also here the SQLite DB? > > Maik > -- You are receiving this mail because: You are watching all bug changes.
