Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High CPU usage (with the caveats) #10773

Open
cyberduck opened this issue Aug 4, 2019 · 1 comment
Open

High CPU usage (with the caveats) #10773

cyberduck opened this issue Aug 4, 2019 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Aug 4, 2019

5ba5968 created the issue

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:

external image

The same using MountainDuck:

external image

and its threads, sorted by CPU usage:

external image

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

external image

external image

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

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 21, 2019

@dkocher commented

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

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants