Database Reference
In-Depth Information
Because there is no local flash resource present, it cannot store it locally; however,
FVP will continue to fetch data from the flash cluster to keep the latency to a minimum
while reducing the overall stress and load on the storage array.
With PernixData FVP, it may be possible to delay the need for costly forklift upgrades
of existing primary storage investments that have reached the end of their performance,
well before the end of their capacity. As we've seen with our RAID calculations, this
can be common for high-performance workloads. FVP can provide much more efficient
use of the deployed capacity and may allow the breathing space required for you to
determine the best next steps for your future storage and virtualization strategies.
Note
PernixData has a demonstration of how it accelerates SQL performance
with-pernixdata-fvp/
. The PernixData FVP Datasheet is available at
The examples in
Figures 6.44
and
6.45
show a SQL 2012 database driving around
7,000 IOPS consistently and the resulting latency both at the data store and at the VM
level. The total effective latency is what the virtual machine sees, even though the data
store itself is experiencing drastically higher latency. In this case, in spite the latency of
the data store being upwards of 25ms, the SQL VM response times are less than 1ms.
Figure 6.44
PernixData FVP acceleration for SQL Server 2012 IOPS.
