Heya folks, Ned here again. A customer contacted us about a strange behavior they were seeing when copying large files to a Windows Server 2019 cluster using SMB 3.1.1. Around every 5GB transferred, ...
Updated Nov 07, 2022
Version 3.0
Blog Post
Tagging NedPyle (as I probably should have done the first time around)...
I haven't been able to get this registry edit to take effect (still seems capped at 5GB), but I notice one difference between your quoted language and their current site:
Your quote:
This threshold can be controlled with the following DWORD registry value name:
Current https://learn.microsoft.com/en-us/windows-server/administration/performance-tuning/subsystem/cache-memory-management/troubleshoot#remote-file-dirty-page-threshold-is-consistently-exceeded:
This threshold can be controlled with the following regkey
Does this mean it should be a key value (i.e. registry folder value) rather than a DWORD value? That doesn't seem to work for me either, though. It still drops to 0 once the modified memory hits 5 GB. This screenshot was taken as it dropped from 5 GB (it's at 4 GB). The transfer resumes when it gets back down to under 1 GB.