Usually, transfer rate is the much more important metric.
However, IF you are supporting a very high rate of IO operations that are
small, a difference in IOPS for infrastructure with the same (or similar)
maximum transfer rates can be important.
Notice that this includes knowing something about the I/O request size you plan
to support, so it is NOT a contradiction of what Tim wrote, and in fact it may
be an edge case. But it is and edge case I have seen. You should definitely be
interested in the transfer rate, but you might also be interested in IOPS
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Tim Gorman
Sent: Tuesday, June 21, 2022 4:50 PM
To: veeeraman@xxxxxxxxx; ORACLE-L
Subject: Re: Data Transfer vs IOPS
As a metric for comparisons, IOPS are useless without I/O request size (or
For example, comparing 20000 IOPS for one disk means nothing in comparison to
10000 IOPS on another disk, unless you know the I/O request sizes used.
In contrast, throughput (a.k.a. data transfer rate) is a comparative metric by
itself, which is probably why Dell uses it.
On 6/21/2022 12:55 PM, Ram Raman wrote:
We are looking into adding some new disks to our server with server attached
storage. One of the solutions we are considering is this
. The page talks about Data Transfer rate but I am interested in the IOPS, we
have the IOPS info for the older disks. Does anyone know how to get the IOPS
(read, write, .. any) for those disks