问题原文
原帖链接 · TomTom · CC BY-SA 3.0
Can not find that anywhere it seems.
What is the expected performance difference in a storage backend scenario that is heavily parallellized in access (like a SAN, Virtualization host storage etc.) between SAS and SATA, all other things being equal?
I Think it runs down to the impact of NCQ (32 command limit) to the MUCH higher oustanding command limit of SAS discs.
We are considering replacing some discs and have a chance to go for SAS or SATA - all the rest is in place - and I look for an evaluation from a performance point. Please ignore all the other issues (reliability etc.) - I purely wonder about the impact SAS will have on similar specced discs (RPM etc. being equal). The discs we have in mind can be ordered with both connectors and - there is an idea here to use SATA for ap ossibly repurpose later. THe price difference is not really high, but it made me wonder about the performance impact...
社区高分解答
原帖链接 · shodanshok · CC BY-SA 4.0
This is a late answer, but I would like to add my opinion.
From a pure speed standpoint, a nearline drive (as the ones OP considered) will performs practically the same both using the SATA interface or SAS interface. Despite the much lower-depth NCQ (31 entries rather than TCQ 64K), this limited hardware queue is sufficient, when augmented with the much deeper software-based IO queue, to extract almost the same IOPS which can be obtained using SAS-based TCQ.
Anyway, this does not means that SAS has no practical advantages:
- much better support for expanders
- support for double-link interface
- full-duplex operation
- much faster maximum signaling rate (12 Gb/s vs 6 Gb/s)
However, when considering performance alone, the sad reality is that mechanical disk's random IOPS values are so low that the interface has almost no impact, excluding huge disk arrays where is can sometime limit your sequential IO transfer rate. Due to how it take rotational delay (which is hidden from the OS) into account, the killer performance-enhancing feature is NCQ/TCQ, and the SATA implementation is sufficiently good at that.
Some more significant differences appear when considering higher end SAS disks, which not only offer higher-RPM disks (10K and 15K), but have some interesting write-coalescing technologies (ie: HGST media cache tech) which, by the way, are slowly spilling into enterprise-SATA drives also.
1 https://ata.wiki.kernel.org/index.php/Libata_FAQ:
However, the ATA standard has a design flaw. The NCQ tag is presumed to be a 32-bit bitmap (32-bit dword). If all 32 tags are asserted, this produces a value (0xffffffff) that is the same value returned by reading a hardware register after the hardware has been hot-unplugged, or suffers a major failure. Thus, to distinguish this condition, libata artificially limits all NCQ configurations to 31 tags rather than 32.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
