Cyberduck Mountain Duck CLI

#10773 new defect

High CPU usage (with the caveats)

Reported by: antiquate Owned by: dkocher
Priority: normal Milestone:
Component: ftp Version: 7.0.1
Severity: normal Keywords: cpu, resources
Cc: Architecture: Intel
Platform: Windows 10

Description

i7-3820QM, 32Gb RAM
Windows 10 Pro 10.0.18362 Build 18362
Cyberduck v7.0.2
MountainDuck v3.1.0

Physical interface is dedicated to the Hyper-V switch, host OS is using virtual one via the "Internet sharing" feature:

> Get-NetAdapter | select Name, MediaType, MtuSize

Name                       MediaType     MtuSize
----                       ---------     -------
Physical                   802.3            1500
vEthernet (ext_switch)     802.3            1500
vEthernet (Default Switch) 802.3            1500

I have noticed that both MountainDuck and CyberDuck use excessive CPU while using protocols that impose small penalty on the traffic.
For example, unencrypted FTP transfer over the 1Gbps localnet:

https://i.imgur.com/Qqb2hdq.png

The same using MountainDuck:

https://i.imgur.com/kVvNxL1.png

and its threads, sorted by CPU usage:

https://i.imgur.com/22S6IlX.png

Lastly, I have noticed that MountainDuck seems to cache content at system drive.
Can this be disabled so application writes directly to a destination?

https://i.imgur.com/ZnXwPwb.png

https://i.imgur.com/ylVjorg.png

While I am not quite familiar with NT-based systems, I am more than happy to help with the debugging of this issue.

Change History (2)

comment:1 Changed on Aug 21, 2019 at 12:50:40 PM by dkocher

You can disable buffering to local temporary location on write in Mountain Duck by unchecking Preferences → Connection → Enable Cache.

comment:2 Changed on Aug 21, 2019 at 1:02:31 PM by dkocher

  • Component changed from core to ftp
  • Owner set to dkocher
Note: See TracTickets for help on using tickets.
swiss made software