Bug 420168

Summary: Browsing SSHFS folders slows down Dolphin user interface
Product: [Applications] dolphin Reporter: Germano Massullo <germano.massullo>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kfm-devel
Priority: NOR    
Version: 19.12.2   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description Germano Massullo 2020-04-16 17:51:56 UTC
If you browse a SSHFS folder[1], for example /tmp/folder in this case, and go into a crowded subfolder like /tmp/folder/foo, Dolphin will slow down a lot the user interface, till being totally unresponsive for some seconds:
- when in detailed view, I noticed that Dolphin takes seems to be working on populating the "size" column, with the number of elements in each subfolder of /tmp/folder/foo
I assume it is working on size column because I can see Dolphin populating the size entry one by one;
- when in compact view I open a folder, Dolphin seems to be working on detecting what is the type of the files, because as soon I get inside I see the files with a "?" (question mark) icon, then Dolphin assigns the correct icon. For example if a file is a text, assign a text icon, etc.
Note:
- I disabled thumbnail preview in Dolphin;
- I am experiencing this problem also when running in a LAN, so it cannot be a bandwidth problem;
- Dolphin CPU usage seems to not grow when the slowness quirk is happening

[1]:
mounted for example with command
sshfs -o cache=yes -o kernel_cache -o compression=no user@192.168.1.40:/zpool_1/foo /tmp/folder
or with a more simpler command
sshfs user@192.168.1.40:/zpool_1/foo /tmp/folder
Comment 1 Germano Massullo 2020-04-21 14:46:15 UTC
In detailed view, I tried hiding the size column, but it did not improve performances
Comment 2 Germano Massullo 2020-05-16 16:34:53 UTC
I tried GNOME Nautilus and it does not freeze while it is slowly populating the "size" column
Comment 3 Germano Massullo 2020-06-06 10:40:43 UTC

*** This bug has been marked as a duplicate of bug 178678 ***