Version: 1.7 (using KDE 4.7.1) OS: Linux Dolphin can be very slow when copying a lot of files. About 5x slower than kde-cp and more than 15x than cp command (in tested environment*). *Environment: C2D @ 1.2GHz, (old school) HDD, 25 666 smal files (~120MiB) Cache flushed before each test. --- Results: 1. Dolphin: Time: ~5m 9s; CPU usage: Dolphin ~60-70% CPU core, kio_file ~30% CPU core (+some dbus-daemon and kuiserver) 2. (kio_file) kde-cp: Time:~1m 5s; CPU usage: kde-cp ~40 % CPU core; kio_file ~40% CPU core; bus-daemon ~15% CPU core and kuiserver ~15% CPU core 3. cp: Time: ~18s; CPU usage: 20-30% Reproducible: Always Steps to Reproduce: ... Actual Results: ... Expected Results: Dolphin shouldn't be much slower than pure kio. http://www.youtube.com/watch?v=M_MDlPa9jeE
Peter, this is not only kio_file bug, also Dolphin's. Please, take a look at Dolphin vs kio results. Regards.
This bug affects me as well. It can be reproduced using Krusader as well. I was copying a lot of small files and in the end my notification box in tray was showing something like "227 804 / 227 805 files" for very long time even though the last file was not that big, I'm sure. Processor usage was almost 100% for 1 core. I'm using Kubuntu 11.10, KDE: 4.7.4, 64-bit system.
Does increasing the value of "maxInstance" property in file.protocol help at all?
(In reply to comment #3) > Does increasing the value of "maxInstance" property in file.protocol help at > all? I haven't tried it yet, but only one kio process is spawned anyhow, so it's far from current max (5).
This bug is still present in kde 15.08
htop says: 20 0 4116M 264M 98M R 121. 4.4 3:37.31 /usr/bin/plasmashell --shut-up 20 0 261M 31496 25900 R 71.2 0.5 1:05.82 /usr/bin/kuiserver 20 0 45008 4864 2296 R 63.7 0.1 1:02.59 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 5477 me 20 0 5936M 100M 59372 S 60.3 1.7 1:40.15 /usr/bin/dolphin 1682
What kind of INFO is required?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!