PernixData Architect – Block Size Breakdown

In my last post about the PernixData Architect software I covered the so called Drill-Down charts. At the end of the post I didn’t go deeper into the details what could have caused that latency spike for this particular virtual machine. And this is what this blog is intended to do.

So we saw a latency spike and at the same time an increased throughput. Using the Block Size Breakdown you can now easily understand how IO-profile has changed and how the block size is impacting the overall virtual machine performance.


As you can see on the chart, the virtual machine latency was defined by the time it took to process blocks with >=256K in size.

PernixData Architect can not only show how the latency is being impacted by individual block sizes, but can also breakdown into how many IOs have been issued with a particular block size.

ArchitectIOPSBlockSize ArchitectMBsBlockSize

As I’ve mentioned earlier, all these details are available on a virtual Machine level. These detailed insights about the actual block sizes a VM is issuing can actually help you help on several fronts.

Does my current storage infrastructure incl. all its components provide enough throughput to process those IO sizes in an adequate time?

With FVP in the picture, this helps to select the optimal acceleration media which will offer the best performance for those workloads. For example, a regular SSD will be limited in terms of throughput due the SATA interface, whereas a PCIe Flash card would offer way more bandwidth. Not to speak of the capabilities memory would offer to fix such a problem.

This can also help tremendously to go into more data driven discussion with the corresponding application owners, to find a way to optimize the IO-profile at the application level.

That’s it for now, more features to cover in future posts!

Print Friendly, PDF & Email

Related Post