B20292 cpu spikes since b20292 due dedup

[Karl_Wester-Ebbinghaus]

Since the upgrade to b20292 the server computer regularly has high cpu use Spikes (hear this due turning up fans) + TM

Caused by dedup feature running ever since in this config. There is not much data changes and dedup optimize for VDI / Hyper-V / vhdx

Anyone else. I will upgrade to the latest tomorrow and report back.

Important to note that the cpu hog in TM is not tied to dedup task but remaining unvisible for the user think so procmon might help.

Volumes are either a mirrored Storage Spaces or Single volumes. All with lastest ReFS.

Anyone else?

[#2]

The issue is that Background Optimization and Priority Optimization are running every hour and even conflict on their schedule. So some optimization jobs queue up but are successful.

I would like to point out there is not much data IO / changes on the drives and I wonder why the release is seems agressive now on the Dedup

affected builds: b20292, b20295

[#3]

you are certainly busy with Ignite. 

here is a screenshot from the PowerShell

again since b20292 it seems like Dedup Optimization is running over and over causing all day long cpu load

The average looks low but this CPU load is only the average of 12 Threads and mainly caused by Dedup process

@Elden Christensen do you know who could help to investigate this uncommon behaviour?

[#4]

Is there anyone seeing the same issue still?

[#5]

The issue seems to get better in a later release currently 20234

[#6]

Hello @Elden Christensen I am afraid the issue is not solved.
I drilled down that it will appear as soon one enable Dedup for VDI use and "Background Optimization", which will keep the server busy the whole day even when there are no relevant changes on the stored vhdx's-

The scheduled optimize jobs are acting fine but the background optimization is running the whole day (starting, completing, starting again) consuming reasonable amounts of CPU time.