Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 395

Poor performance on storage spaces 2019

$
0
0
Hello everyone. I've been doing some testing of a planned implementation and ran into an issue with Storage Spaces on WS2019. The issue lies in the performance of Tiered Storage on WS2019, it's a complete disaster. With thoughs about a possibility of doing something wrong, I made a decision to built the same configuration on WS2016 and managed to get decent results.
What was the hardware i used? The configuration was based on a:
Single DELL R540 chassis with 2x 4110 (2.1G, 8C/16T), 64GB of RAM, a Perc H730 (configured in HBA mode), 2x 480GB SSD SATA Mixed Use, 3 x 2TB 7.2 RPM NLSAS.
Which WS builds were used? WS2016 Datacenter build 14393 and WS2019 Datacenter build 17763.
How was the tiered storage configured? Virtual volume with simple resiliency, fixed provisioning, NTFS, 4096 allocation unit size creaatod on top of 2x storage tiers - 4x 480GB SSD, 3x HDD 2TB, both with parity layout.
How did i come to the conclusion? I tested 4k and 64k blocks, both random and sequential reads/writes by using the DiskSpd utility with the following paramaters – 8 threads, 16 Number of IO, test file size - 50, duration - 60 sec, warmup - 5 sec.

Results of the tests:

https://imgur.com/a/NHpIBfM

So, to make my consern clear, I need to understand if it is the known issue or did I do something wrong, or does my configuration needs to be modified in some kind of way. Any help will be greatly appreciated.



UPD:

I've also collected the statistics on how much the SSD tier was getting used. I found that SSD tier was not utilized at all. I used Get-Counter cmdlet.
Hoping to see the difference, I also tested the mirror layout on WS 2019, but nothing have changed. Performance was still a disaster. Here are the results:

https://imgur.com/a/l5r0PYV


Viewing all articles
Browse latest Browse all 395

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>