-
When using Mountainduck I'm constantly having very high CPU load between 150% and 750%. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments
-
i am having the same issue, CPU 600-1,000%, even after I disconnect from any open connection. |
Beta Was this translation helpful? Give feedback.
-
Also with the latest update the issue persists |
Beta Was this translation helpful? Give feedback.
-
The same is happening for me. It's been a persistent problem for several app updates, but I've finally grown tired of it and am trying to find a solution. I will mount my SFTP drives, and when I first come in to work the next day, I'll see Mountain Duck using 600% CPU until I kill it and remount. I submitted a log file to support via e-mail but am adding my "me too" here. |
Beta Was this translation helpful? Give feedback.
-
i thought that the issue was an intel mac but it happens on my M1 Max and M1 Ultra macs as well..
that's insane... |
Beta Was this translation helpful? Give feedback.
-
There are several reasons that can cause unexpectedly high CPU usage but in general it indicates an application is accessing files on the mounted volume very frequently. For example this could be:
Another culprit can be the Index Files option set in Preferences → Sync for volumes with a large folder structure with a remote server where on cannot determine if contents of folders has changed. This applies to object storage such as S3. When connected to SFTP volumes, make sure there are no symbolic links that point to a parent or working directory causing folders to be indexed recursively. When all the above does not apply please send a thread dump to support:
|
Beta Was this translation helpful? Give feedback.
-
What was the actual solution here? |
Beta Was this translation helpful? Give feedback.
-
Relates to 1. Footnotes |
Beta Was this translation helpful? Give feedback.
There are several reasons that can cause unexpectedly high CPU usage but in general it indicates an application is accessing files on the mounted volume very frequently. For example this could be:
.noindex
on the mount volume path set by default.Another culprit can be the Index Files option set in Preferences → Sync for volumes with a large folder structure with a remote serve…