Bug 423082 - Dolphin on mounted samba share slow whilst copying file
Summary: Dolphin on mounted samba share slow whilst copying file
Status: CONFIRMED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 20.04.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on: 423481 423487 423492 423499 423500 423502 423532 423501
Blocks:
  Show dependency treegraph
 
Reported: 2020-06-17 05:32 UTC by Unknown
Modified: 2020-06-26 10:24 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Video of the effect. (398.79 KB, video/mp4)
2020-06-17 05:32 UTC, Unknown
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2020-06-17 05:32:10 UTC
Created attachment 129437 [details]
Video of the effect.

SUMMARY
Whilst copying a large file to a network share, the Dolphin  GUI is extremely slow and unresponsive; even when resizing windows or accessing menu bars.

STEPS TO REPRODUCE
1. Copy a large-ish file to a mounted samba drive
2. Open the folder
3. Attempt to use *any* part of dolphin (even window resize redraws are slow)

OBSERVED RESULT
GUI locks up.

EXPECTED RESULT
Should work just as normal (and if it's a task trying to index something, don't run in the main thread).

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.19.1
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0
Kernel Version: 5.7.2-arch1-1
OS Type: 64-bit
Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
Memory: 5.8 GiB of RAM
Graphics Processor: AMD RAVEN

ADDITIONAL INFORMATION
Comment 1 Harald Sitter 2020-06-26 10:19:05 UTC
There is a mountain of issues contributing to what you see. Primarily this comes down to previews being enabled, albeit not exclusively. If you disable previews I'm sure things will behave better, there'll likely still be stuttering though.
The problem here is that POSIX IO APIs are synchronous in behavior. So by mounting a remote file system you essentially make all software address it through those blocking calls and they then can take aaaaages to finish.
The blocking API call is subject to network latency/bandwith constraints and the remote's IO latency/bandwith constraints, and that is why you get intermittent blocks. It's simply waiting for replies. This is always a problem with mounted remote file systems, but in this case its made more prominent because your file copy causes an exhaustion of one of the constraints making the requests take so long that you can notice the UI intermittently locking up.
Comment 2 Unknown 2020-06-26 10:24:19 UTC
Okay, that makes sense.
Thanks for all the bug reports :P