Recommended ssd size for windows 10 keygen#
If this is a production server you really should be considering virtualizing it. Note: A 64K strip size is the recommended size for Hyper-V should you decide to virtualize down the road. And second, hardware RAID controllers are going to write data wherever they please and there is nothing you can do about it. First, you are using SSD's and fragmentation is not an issue with them because they have no moving parts. This is small enough as to not waste a lot of space, yet large enough where performance with large files should be satisfactory.Īs far as fragmentation, don't worry about it. If it is strip size that the controller uses, in your case (120KB - 330KB average file size) I would go with 64K which will give you a 128K stripe size. An array "stripe" is very much like a file system cluster, in that it can only hold a single file, or portion of a single file. You will need to find out whether you are inputting a "strip" or "stripe" size. This is why I asked you about the server make and RAID controller model. When setting up a RAID array, most controllers that I have worked with (LSI, which Dell and some HP controllers are based on) have you enter the "strip" size. Note: Because you are using SSD's, RAID 5 would be an acceptable choice here because SSD's do not have the URE issues that HDD's have and their increased speed lessens the rebuild time, and the performance impact on the array when degraded and rebuilding. A RAID 0 would be strip size x 4, RAID 5 would be strip size x 3. In your case, a 4 disk RAID 10, it would be strip size x 2 because of the mirroring. Then there is the "stripe" size which is equal to the strip size x the number of drives in the stripe. There is the "stripe element" size (often referred to as "strip" size) which is the per drive size. There are two different "stripe" sizes involved here. What is the server make and what RAID controller are you using.