A J Holland Jones
2 discussion posts
I use the Desktop Wallpaper part of display fusion to manage my wallpapers for my dual displays. I have it set to change both wallpapers every 60 seconds, the folder I have it set to pull wallpapers from contains ~115, 000 wallpapers. The CPU usage of display fusion is normal @ 1% but when it becomes time to select a new wallpaper the CPU usage spikes to ~20-25% then the wallpapers change and the usage drops down to normal.
A J Holland Jones
2 discussion posts
i guess the reason why i made the post initially was not because i wanted to distribute the CPU load more evenly but rather because i feel that possibly maxing one core for a program that is designed to run all the time on you computer isn't quite right. How displayfusion is getting the file list and what it does with it after is the problem, does it cache the list? does it remake it every time? For ~115,000 files this is clearly quite costly in terms of processing time, could this be optimised? can the list be generated only once every X amount of time. i feel these are better things to consider.
We've looked into it in the past, and the majority of the CPU usage comes from the .NET image generation library when the wallpaper itself is stitched, cropped, and resized. Are you running into any issues when the wallpaper changes?