GNOME Bugzilla – Bug 792331
High CPU load after mounts changes
Last modified: 2018-02-01 11:33:02 UTC
This is part of my effort to reduce CPU load during mass changes of mounts...
See bug for g-s-d: https://bugzilla.gnome.org/show_bug.cgi?id=792235
Created attachment 366495 [details] [review] trash: Rate limit mounts_changed signal The gvfsd-trash daemon can cause high CPU load for a quite long time in situations when it recieved a big amount of mount_changed signals within a short time. This can easily happen in enterprise environments where autofs mounts are havily used. Use g_unix_mounts_changed_since to check whether the mounts changed since the last check to prevents high CPU load after the last real change, because the processing is slow and the daemon is not able to handle the signals in real time. Also let's limit the number of checks per time to reduce CPU load.
See also trash monitor improvements: https://gitlab.gnome.org/GNOME/nautilus/merge_requests/57 https://bugzilla.gnome.org/show_bug.cgi?id=792331
Was hopefully fixed by: https://bugzilla.gnome.org/show_bug.cgi?id=793006