We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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:
The same using MountainDuck:
and its threads, sorted by CPU usage:
Lastly, I have noticed that MountainDuck seems to cache content at system drive.Can this be disabled so application writes directly to a destination?
While I am not quite familiar with NT-based systems, I am more than happy to help with the debugging of this issue.
The text was updated successfully, but these errors were encountered:
@dkocher commented
You can disable buffering to local temporary location on write in Mountain Duck by unchecking Preferences → Connection → Enable Cache.
Sorry, something went wrong.
We have been unable to reproduce the problem in recent versions. Please open a discussion if you still require assistance.
@dkocher I am able to reproduce it. Just limit the file transfer speed and you will see the CPU usage skyrocket!
dkocher
No branches or pull requests
Physical interface is dedicated to the Hyper-V switch, host OS is using virtual one via the "Internet sharing" feature:
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:
The same using MountainDuck:
and its threads, sorted by CPU usage:
Lastly, I have noticed that MountainDuck seems to cache content at system drive.
Can this be disabled so application writes directly to a destination?
While I am not quite familiar with NT-based systems, I am more than happy to help with the debugging of this issue.
The text was updated successfully, but these errors were encountered: