This was the part I was upset the most about (not the cpu-time, but I didn't have my tools set to show page-faults/s when I posted earlier). Most computers have a limited number of megabytes of cpu-cache. For Core i7's it's 8-10MB for all the cores to share (6-. For Desktop Xeons, it can run from 12-15MB all the cores to share. But @ a burn rate of 2.5MB/s, DisplayFusion will kick other, less-active programs out of the cache every 4-6 seconds. Note, this is with all features turned off except changing the wall paper every *DAY*.

When I contacted support about the high cpu usage for an idle program, I was told it was only about 0-1% with everything turned on, on their system. When I told him that program cpu usage was divided by # of cores on the machine (versus DF using only 1 core as it is limited to with the affinity) and asked how many cores his machine had - I got no response. Today's higher end desktops have 8 cores at the higher end (it changes so fast I have a hard time keeping up with the max cores), meaning DF uses an average 6% of it's core -- when it is supposed to be asleep. Why? (Note: since MS's cpu display doesn't show fractions, 0=(0-.499%) & 1=.5-1.49999% = .25-1% = 4-8% of 1 core or ~6% (using middle number)).

Why isn't DisplayFusion completely silent/inactive? Why does it need to burn though cpu and invalidate that much cpu cache when it is supposed to be asleep?

Is it doing something other than changing WP every 24hours? Sure seems to be. :^(