| Summary: | high load when tagging | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Arnd Baecker <arnd.baecker> |
| Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.7.0 | |
| Attachments: | prevent kio_digikamalbums/dates (etc.) when database file is changed | ||
Created attachment 27339 [details]
prevent kio_digikamalbums/dates (etc.) when database file is changed
Marcel pointed out to me on the mailing list that for 0.10, a solution
has been implemented.
The attached patch is a modified backport from the KDE4 version,
which ensures that data-base changes don't trigger a rescan.
Hi Arnd, I've just checked your patch, works fine here... as Marcel mentioned on the ML: I guess you can just apply the patch. Andi Fixed in r863588. Problem not reproducible since digiKam 5.0.0 as all KIO slave have been replaced by a multithreaded interface to query the database. |
Version: (using KDE 3.5.9) OS: Linux Installed from: Ubuntu Packages When associating tags, I encounter a substantial CPU load, caused by (sometimes several) kio_digikamdates and kio_digikamalbums processes. The origin of this seems to be the following: At some point one gets on the konsole: "Noticed file change in directory /home/username/Pictures" (i.e. the directory containing the database!) this then triggers DIO::scan which then calls in dio.cpp in void Watch::slotDone(KIO::Job*) Digikam::AlbumManager::instance()->refresh(); Digikam::AlbumLister::instance()->refresh(); I.e. those which then lead to the invocation of kio_digikamalbums and kio_digikamdates.