
sandmann
65 discussion posts
DisplayFusion currently refreshes the wallpaper image list every time the wallpaper image changes.
The DisplayFusion Photos Screen Saver has a setting "Refresh Image List After: (minutes)" that allows the user to specify how often DF should enumerate the local directories. This image library does not have a high rate of change so I set this to "9999" (its max value) to minimize disk and CPU usage.
The Wallpaper image library similarly does not have a high rate of change. But with large image libraries, monitor splits, multiple monitors, the CPU and disk usage can be extremely high. A 100,000 image library and a single monitor in a 2x2 split will cause 4 directory enumerations of 100,000 files each. (Or if each monitor split has a unique library.)
This is wasteful and unnecessary in the vast majority of cases. Especially in a wireless network environment if the images are on a network drive.
Instead, add a setting allowing this to be user-configured. If unset, the current behavior is maintained. Set to 0 (zero) to tell DF to only refresh the image list when it starts. Or up to 9999 minutes between refreshes.
Extra unnecessary thoughts: I know DF displays a message "Warning: Setting your wallpaper change interval to less than 1 minute may cause frequent disk usage" when you do this. I have it set to 1 minute because anything less makes my system unusable. Even with this, at about the midpoint between wallpaper changes, 30-32 seconds, the UI on my computer freezes, by which I mean characters I type do not display for 2-3 seconds; I can move the mouse pointer but clicks do not register immediately; and so on. (As far as I can tell, underlying system processes do not seem to be affected.) The problem gets worse as the day goes on (UI freezes for 10-20 seconds). The only solution is to log-off and log-on again, that seems to free up the resources DF is consuming. Depending on what I am doing, I might have to do this as often as every 3 to 4 hours. If I disable DF wallpaper changes there are no problems.
One more nail, these constant extra directory enumerations also increase writes to SSDs, which have a finite write limit.
And lastly, older posts described periodic CPU spikes which your developers spent a lot of time trying to track down. Were any of the causes wallpaper directory enumeration?
Thanks.