We’ve done a lot of work on Storage Spaces recently to try and find out why our new parity array on server 2019 was slow.
The hardware is the following:
12x 8TB 7200RPM 512e drives
When creating the Storage Space, the logical sector size is set from the disk. These disks are 512e drives with a 512 sector size. The default sector size created is 4k.
You can either buy native 4k drives at the outset, or set your Storage Space to 4k.
Here is our storage spaces before the change:
From my techs
By default when creating a storage pool, the logical sector size should match the highest physical sector in the disk pool, in this case it should be 4K, but maybe due to this drive is 512e drive, so the logical sector stays in 512. This will cause 8 times delay and performance delay due to the OS and disk controller is doing so called “RMW” operation. The picture below described how the performance get affected by this way.
Once we change our Storage Space to 4k, we started to get 120-160mb/s across the array, all the time. Before this, we were getting 30-60mb/s with many stutters.
Earlier in the month Microsoft announced their new subscription service for Windows 10 Enterprise. Starting at just $7 USD per month, end users are able to subscribe to Windows 10 enterprise on a monthly basis.
This, I think, is a good move by Microsoft.
However, what is disturbing is what Microsoft is changing on lower tier versions, such as Windows 10 Professional. See the following changes:
I’d say this is to target the small business users who now cannot disable the shop within Windows. This will push slightly larger businesses to go to Enterprise.
While a small change, I hope Microsoft doesn’t fall into the trap many other monthly subscription providers have fallen into.
You may have come across this issue when you’ve upgraded your computer to Windows 10. Upon returning to your computer, the screen refreshes slowly and applications appear to have crashed due to memory issue.
There have been many suggest ways to fix this, but the simplest way is to do the following:
Open Regedit by pressing Windows Key + R and typing regedit
Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management
Change the value of ClearPageFileAtShutDown to 1
Reboot your computer
This will wipe the page file on reboot.
This may increase the shutdown time of your computer, but it will fix this error. The root cause of this error is an incompatible driver on your system. I will follow up with an article on this process.