Bug 245125 - Sorting keeps too much time on mounted network filesystems
Summary: Sorting keeps too much time on mounted network filesystems
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-07-19 12:58 UTC by tony
Modified: 2018-10-27 03:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tony 2010-07-19 12:58:13 UTC
Version:           unspecified (using KDE 4.4.4) 
OS:                Linux

In dolphin, clicking on a column like "size" on a real mounted network filesystem (not kio_sftp or similar) takes too much time.
On a E7500 core2 duo @ 2.93Ghz i have to wait seconds for dolphin to do a simple sorting operations on a bunch of items if they are on a mounted network filesystem (like cifs or sshfs).
Sorting 1000 items on an 10MBps line can take a minute or so.

Reproducible: Didn't try

Steps to Reproduce:
-mount a remote filesystem on a 10MBps link
-create or copy 1000 non empty folders to it
-try to sort the list by size



Actual Results:  
-you have to wait too much time
-in the meantime dolphin is unresponsive
-you can't open another dolphin instance.
-you can't even continue to work on other dolphin instances

Expected Results:  
-to wait less than a second
-those operations should not block dolphin nor other dolphin instances.
Comment 1 FiNeX 2010-08-02 14:26:31 UTC
I can confirm a big difference between a samba share mounted locally and kio_smb.

Opening a mounted share with 10.000 files needes about 20 seconds. opening the same directory using smb:// (kio) needs about 1-2 seconds. 10 times faster.

Anyway, after the directory has been loaded I've not noticed particular slowdown ordering the files.
Comment 2 FiNeX 2010-08-12 20:53:01 UTC
It looks that a similar issue exists in KDE 3 too: bug #247326
Comment 3 Dawit Alemayehu 2013-06-18 05:25:54 UTC
There has been lots of improvements in every part of KDE since 4.4. Is this still an issue in the latest stable version of KDE, v4.10 or higher?
Comment 4 Andrew Crouthamel 2018-09-24 02:12:19 UTC
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!
Comment 5 Andrew Crouthamel 2018-10-27 03:48:41 UTC
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!