Feb 18 2021 03:25 PM
Mar 01 2021 12:00 PM
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
Mar 02 2021 11:04 AM
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
@EldenChristensen do you know who could help to investigate this uncommon behaviour?
Mar 21 2021 05:22 AM
Apr 08 2021 01:32 AM
Apr 24 2021 12:11 PM - edited Apr 24 2021 12:13 PM
Hello @EldenChristensen 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.