Bug 329353 - Make slow processing better
Summary: Make slow processing better
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Maintenance-Thumbs (show other bugs)
Version: 3.4.0
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-29 09:00 UTC by julien.t43+kde
Modified: 2019-09-15 07:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.4.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description julien.t43+kde 2013-12-29 09:00:41 UTC
On my netbook (or could be the same with large/big collections), on multiple occasions, the processing could be very slow and the interfaces gives little feedback to check if not crashed and make it more manageable, especially by treating small files first and giving back interface/interactivity quickly. I have time where initial scan takes hours and I can do nothing else...
Most of this stuff should either be default or advanced opion only/digikamrc probably

- when scanning for thumbnails (initial scan, maintenance), option to skip or delay at the end file bigger than X mb (default: 10MB?; if bigger, at first start, check cpuinfo/meminfo and if small, offer to adjust or settings checkbox)
- in preview/thumbs bar, if loading image take more than 3 sec, infobubble/message "Loading <filename>"
- option to limit kio subprocess active at the same time: had time when half-dozen kio_digikam* where fighting for my poor cpu... maybe a limit of one or two per core, especially for Atom processor
- set process and subprocess to idle priority (cpu/nice and disk/ionice) when minimized

Test up to 3.5 (lubuntu 13.10/kde 4.11.3 and before, macos 10.9).

Reproducible: Always
Comment 1 caulier.gilles 2016-07-04 13:58:51 UTC
With 5.0.0 release, we drop KIOSlaves and use multithreading everywhere.

This file still valid using digiKam 5.0.0 ?

Gilles Caulier
Comment 2 caulier.gilles 2016-11-25 20:16:40 UTC
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 3 Mario Frank 2017-02-22 15:10:48 UTC
Git commit 2f8ddd42ef62d7aea9e490cdb05ffcc644810c81 by Mario Frank.
Committed on 22/02/2017 at 15:05.
Pushed by mfrank into branch 'master'.

Merged the current state of the garbage collection branch which improves the database cleanup stage of the maintenance
and improves the reactiveness of the maintenance overall. We ported the way items are processed to a queue based method
that can use the CPUs more effectively and does not create thousands of threads.
Related: bug 283062, bug 216895, bug 374225, bug 351658, bug 362023
FIXED-IN: 5.5.0

M  +17   -12   NEWS

https://commits.kde.org/digikam/2f8ddd42ef62d7aea9e490cdb05ffcc644810c81
Comment 4 Maik Qualmann 2019-09-15 07:01:25 UTC
Git commit e6e76cf0cf8b34f028511958070f98f457eef81a by Maik Qualmann.
Committed on 15/09/2019 at 06:47.
Pushed by mqualmann into branch 'master'.

less locked database during the initial scan
Related: bug 389949, bug 411927
FIXED-IN: 6.4.0

M  +3    -1    NEWS
M  +8    -4    core/libs/database/collection/collectionscanner_scan.cpp

https://invent.kde.org/kde/digikam/commit/e6e76cf0cf8b34f028511958070f98f457eef81a