B20292 cpu spikes since b20292 due dedup

%3CLINGO-SUB%20id%3D%22lingo-sub-2147781%22%20slang%3D%22en-US%22%3EB20292%20cpu%20spikes%20since%20b20292%20due%20dedup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2147781%22%20slang%3D%22en-US%22%3ESince%20the%20upgrade%20to%20b20292%20the%20server%20computer%20regularly%20has%20high%20cpu%20use%20Spikes%20(hear%20this%20due%20turning%20up%20fans)%20%2B%20TM%3CBR%20%2F%3E%3CBR%20%2F%3ECaused%20by%20dedup%20feature%20running%20ever%20since%20in%20this%20config.%20There%20is%20not%20much%20data%20changes%20and%20dedup%20optimize%20for%20VDI%20%2F%20Hyper-V%20%2F%20vhdx%3CBR%20%2F%3E%3CBR%20%2F%3EAnyone%20else.%20I%20will%20upgrade%20to%20the%20latest%20tomorrow%20and%20report%20back.%3CBR%20%2F%3E%3CBR%20%2F%3EImportant%20to%20note%20that%20the%20cpu%20hog%20in%20TM%20is%20not%20tied%20to%20dedup%20task%20but%20remaining%20unvisible%20for%20the%20user%20think%20so%20procmon%20might%20help.%3CBR%20%2F%3E%3CBR%20%2F%3EVolumes%20are%20either%20a%20mirrored%20Storage%20Spaces%20or%20Single%20volumes.%20All%20with%20lastest%20ReFS.%3CBR%20%2F%3E%3CBR%20%2F%3EAnyone%20else%3F%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2147781%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ededuplication%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor
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?
0 Replies