Bug 381605 - Importing large image collection slows down to unacceptable speed
Summary: Importing large image collection slows down to unacceptable speed
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-Gphoto2 (show other bugs)
Version: 5.5.0
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-24 13:26 UTC by Piotr
Modified: 2017-08-18 05:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.7.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr 2017-06-24 13:26:18 UTC
There is something wrong with import - speed.

My setup is laptop + NAS. 

On laptop's local SSD drive I have digikam.db, NAS (Synology) is a datastore for images.

When I copy images from laptop to NAS (using dolphin) the average speed is 20-50MB/s. The same set of images imported from MPT device (Samsung smart phone, connected with USB) or local folder on SSD drive (using CTRL+ALT+I) makes the process sloooow. When I monitor the LAN speed during import I can see weird behavior. Net usage is generally very low, with some occasional peaks. From DK point of view I can see progress, but it is very very slow. The first images are going well, but soon (3-4%) there is huge slowdown and it forces me to interrupt the process.

The scale of import is about 350 images/video files (10GB of data).

My system is Kubuntu, Digikam package from Phillip5 ppa.

Regards
P.
Comment 1 caulier.gilles 2017-08-17 20:57:34 UTC
To perform this MTP operation you pass through the Gphoto2 driver. Try the USB Mass Storage way, it will be faster.

Gilles Caulier
Comment 2 Piotr 2017-08-17 21:49:45 UTC
To use mass storage USB I had to remove SD card from my smartphone which is not a convenient way. But what can I say now (DK 5.6) is that importing from smartphones works better = with good speed when it finally connects to system. Anyway MTP is terrible and cumbersome. 

I don't now why it started to work more or less reliably, but for now we can close this bug I guess.
P.