![]() ![]() I would have to have different arrays for each (which I also assume means different parity drives for each array).įrom what I can tell, these are some pros and cons, and I'm positive this list is not all-inclusive. Also my understanding: I cannot mix SAS and SATA in the same array. Does one have benefits over the other? The primary purpose is going to be a storage array for Jellyfin, but will also likely house some central storage for other VM's (yet t be implemented). I know that SATA speeds are probably more than enough, but I can get SAS for the same price. At present, SATA SSDs are popular because of their cost-effectiveness. That said, the sweet spot seems to be about 12TB for me right now, and I have two options: SAS 12Gb/s and SATA. To choose the right SSD for different server workloads, the IT managers should know the pros and cons of the common SSD interface. I have a plethora of 2TB drives (almost enough to fill this case), but that's a lot of electricity for relatively little storage space, considering I can get all of those down into as little as a single drive (should I spend the money). In this video we will be taking a look at three storage connectors that are currently in the market We break down all three to help you understand what they. In an effort to start populating this beast of a case, I plan on buying some newer, larger hard drives (8TB & up). ![]() I also took advantage of (but have not yet implemented) the Black Friday sale for the Lifetime Pro License of Unraid. I plan on swapping out the motherboard to something slightly newer (but not a ton), some socket 2011 v2's. Given this, it's not very clear why there's even any market for 10k/15k SATA HDDs anymore - especially given that the capacities of these 10k/15k SAS HDDs are relatively similar and often even smaller than the capacities of the SSDs.I was gifted an old SuperMicro 846 24-bay server with a TQ backplane and some old Opterons. However, random IO is uncomparable - SSDs are faster by a factor of about 400x (4 hundred times). This adapter is just a passive strait-through cable with an SAS connector on one end and a SATA connector on the other, it does not perform any signal/protocol/interface conversion. ![]() The SATA ports on a typical motherboard are not going to work. Of course, sequential speeds of 15k SAS HDDs (at about 250MiB/s on the outer physical layer (the beginning of the logical disc), and 100MiB/s on the inner layer (at the end of the logical disc)) are still relatively competitive with SATA SSDs (which usually do about 500MiB/s sequential throughput), because SSDs are reaching interface limits (6Gbps SATA is limited to 600MiB/s due to the 10/8 encoding) the difference is merely a factor of about 2 to 4x, whereas SAS HDDs would provide higher reliability. You need an SAS controller (HBA) to talk to an SAS drive. At random 4K read/write, that translates to 340MiB/s, which would appear to be faster than even the sequential speeds of latest-generation HDDs. (These IOPS parameters are limited by the speed of rotation, which stays constant through generations, and doesn't improve with each generation (unlike sequential throughput, which does improve with each generation).) Doing simple math around random 4K reads/writes, this translates to a performance metric of at most 800KiB/s - well under 1MiB/s.Ĭompare this with the specs for various SSDs that have been on the market for a number of years generally, the SATA 6Gbps (600MiB/s) ones appear to have reached interface limit, as they all appear to be spec'ed to about 85k IOPS for both reads and writes. At HDD: performance differences between 7.2k SATA and 15k SAS, we've determined that 7.2k RPM HDDs would have well under a 100 IOPS, whereas even 15k SAS would still only net you about 200 IOPS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |