https://bugs.kde.org/show_bug.cgi?id=384561
Bug ID: 384561
Summary: Dolphin copy operation is 4,5x slower than cp
Product: dolphin
Version: 17.08.0
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: massimocalleg...@yahoo.it
CC: elvis.angelac...@kde.org
Target Milestone: ---
KDE Neon 5.10, KDE Frameworks 5.37.0, Qt 5.9.1, Dolphin 17.08.0
Source filesystem: ext4
Target filesystem: NTFS
Prepare a copy test folder with 5 large files like this:
# mkdir copytest
# cd copytest/
# for i in `seq -w 1 5`; do dd if=/dev/urandom of=file-$i.bin bs=1M count=4196;
done
# cd ..
First observation: if Dolphin is open on 'copytest' during the above operation,
it hangs until the operation is finished.
Copy test folder with the cp command like this:
# date; cp -r copytest/ /media/user/ExternUSBDrive/; sync; date
On my PC I got:
sun 10 sep 2017, 13.40.14, CEST
sun 10 sep 2017, 13.47.36, CEST
Total time: 7 minutes, 22 seconds
Do the same operation with Dolphin:
- right click on 'copytest' -> Copy
- go to external USB drive
- right click -> Paste
- minimize Dolphin
- don't do anything else and watch the green bar slowly progressing
Total time: 31 minutes, 12 seconds
The CPU usage is ridicolous too: cp stays around 20%, while Dolphin stays
around 40%
This is an example with just 20GB of data, which is nothing nowadays. Sometimes
it occurs to me to copy 150GB of data, which would mean something like 53
minutes (cp) against more than 4 hours (Dolphin)
I suspect there is a severe issue with KDE filesystem watchers, which is the
only thing that can make the difference in such a basic operation where you
just need to do fread -> fwrite.
However, I'd expect that minimizing Dolphin would disable every FS watcher.
--
You are receiving this mail because:
You are watching all bug changes.
