Forum Discussion

uedgars's avatar
uedgars
Copper Contributor
Nov 22, 2018

Server 2019: Poor write performance on S2D two node cluster

Hello!   I am trying to set up S2D on two node cluster for Hyper converged infrastructure. Unfortunately I observe significant write performance drop if we compare S2D storage with slowest physical...
clustering
Storage
Windows Server
Girdhar's avatar
Girdhar
Icon for Microsoft rankMicrosoft
Dec 14, 2018

Thanks for evaluating S2D Clusters on Server 2019.

This configuration does not meet the fundamental requirement of S2D, as:

  • SSDs used are non-PLP, and
  • Nodes are heterogeneous.

 Please go over this blog, https://blogs.technet.microsoft.com/filecab/2016/11/18/dont-do-it-consumer-ssd for more details.

 

Also, please refer this article as well, on evaluating storage perf:

https://blogs.technet.microsoft.com/josebda/2014/08/18/using-file-copy-to-measure-storage-performance-why-its-not-a-good-idea-and-what-you-should-do-instead/

 

~Girdhar Beriwal

  • uedgars's avatar
    uedgars
    Copper Contributor
    Jan 09, 2019
    Hello!

    Thank You about Your comment! I understand, that my lab setup does not meet these requirements, but still I believe that fundamental thinks should work with such a setup too. The main point for me was to check if this tehnology works before invest into new and quite expensive parts.

    Anyway, now I have rebuilt my setup using two intel S2600WTF/Y boxes and Intel CPUs. Initially each of them had two 512 GB SSD drives for S2D. I configured S2D with automatic settings successfully. After providing some performance tests I got much better results than earlier. Actually really acceptable results (even up to little more than 200MB/s write speed).

    Next I moved some VMs to the S2D and enabled High Availability for them. I provided some crush tests as well and they succeed, all worked great.

    BUT then I faced new problems. I wanted to add four new 1 TB SSD drives per each node and extend my pool. I did reset all these drives and connected to servers.
    1) First strange thing was, that they automatically were added to my S2D pool even I was previously disabled autopooling (Get-StorageSubSystem Clu* | Set-StorageHealthSetting -Name “System.Storage.PhysicalDisk.AutoPool.Enabled” -Value False).
    2) Second and the most important - my SSD tier statistics shows available space only for 670 GB, but I connected 8 x 1TB SSD drives and using mirrored storage it should be able to allocate around 4 TB! I run Optimize-StoragePool and this did not helped.
    3) I connected another SSD drive for other purposes and it again automatically got pooled. I tried to remove it from S2D pool, but this also was unsuccessful. The disk stuck into Primordial Pool. Things I did to try to get disk out of pool:
    $pool = Get-StoragePool S2D*
    $disk = Get-PhysicalDisk -SerialNumber "XXXXXXXXXXXXXXXXXXX"

    $disk | Set-PhysicalDisk -Usage Retired

    $vdisk=Get-VirtualDisk

    Repair-VirtualDisk $vdisk.FriendlyName

    Get-StorageJob

    Get-StoragePool S2D* | Remove-PhysicalDisk -PhysicalDisks $disk

    Set-ClusterS2DDisk -CanBeClaimed $true -PhysicalDiskGuid $disk.UniqueId

    $disk | Reset-PhysicalDisk
    • Girdhar's avatar
      Girdhar
      Icon for Microsoft rankMicrosoft
      Jan 16, 2019

      Can you please send the output of following cmdlets:

      1. Get-StoragePool

      2. Get-PhysicalDisk

       

      ~Girdhar

      • uedgars's avatar
        uedgars
        Copper Contributor
        Jan 18, 2019

        Hi, Girdhar!

         

        I physically removed from server the disk that accidentally went into S2D and then stuck in Primordial pool. Then I cleared it on another PC and created new partition. Then put back in cluter server and finally had option to use it without pooling.

        But I plan to replace s2d 512 GB ssd driveswith larger ones so I still need to find option how to correctly remove disk from pool.

        PS C:\Windows\system32> Get-StoragePool

         

        FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly Size AllocatedSize

        ------------ ----------------- ------------ ------------ ---------- ---- -------------

        Primordial OK Healthy True False 72.9 TB 9.31 TB

        S2D on hc-cluster-1 OK Healthy False False 9.31 TB 1.84 TB

        Primordial OK Healthy True False 11.53 TB 9.31 TB

        　

        　

        PS C:\Windows\system32> Get-PhysicalDisk

        DeviceId FriendlyName SerialNumber MediaType CanPool OperationalStatus HealthStatus Usage Size

        -------- ------------ ------------ --------- ------- ----------------- ------------ ----- ----

        22 ATA INTEL SSDSC2BB24 PHDV7171021B240AGN SSD False OK Healthy Auto-Select 223.57 GB

        1004 Samsung SSD 850 PRO 512GB S250NSAG432476E SSD False OK Healthy Auto-Select 476.94 GB

        1003 Samsung SSD 840 PRO Series S1AXNSAD800683Y SSD False OK Healthy Auto-Select 476.94 GB

        1010 Samsung SSD 850 PRO 1TB S252NWAG304907F SSD False OK Healthy Auto-Select 953.87 GB

        2016 Samsung SSD 850 PRO 512GB S250NSAG432479X SSD False OK Healthy Auto-Select 476.94 GB

        1009 Samsung SSD 850 PRO 1TB S252NEAG301324Y SSD False OK Healthy Auto-Select 953.87 GB

        2015 Samsung SSD 840 PRO Series S1AXNSAF111936H SSD False OK Healthy Auto-Select 476.94 GB

        1008 Samsung SSD 850 PRO 1TB S252NWAG304891D SSD False OK Healthy Auto-Select 953.87 GB

        2000 ATA Samsung SSD 850 S1SRNWAF913328T SSD False OK Healthy Auto-Select 953.87 GB

        1007 Samsung SSD 850 PRO 1TB S252NWAG403194P SSD False OK Healthy Auto-Select 953.87 GB

        2019 ATA Samsung SSD 850 S1SRNWAF914370B SSD False OK Healthy Auto-Select 953.87 GB

        2020 ATA Samsung SSD 850 S2BBNEAG113774L SSD False OK Healthy Auto-Select 953.87 GB

        2021 ATA Samsung SSD 850 S2BBNEAG113775K SSD False OK Healthy Auto-Select 953.87 GB

         

         

         

Resources