Improvements
With the release of Purity 5.3 there was an upgrade to the backend database service on the FlashArray. What is Different about Purity //FA 5.3 for vVols? and how these backend changes help out vVols and VASA overall. There is a Terminology Review now as well that would be good to review as the impact of the changes in VASA 1.1.0 and Purity 5.3 can be understood better with that knowledge as well. While the improvements to database service are found in all versions of Purity 5.3, VASA is not fully taking advantage of those changes until 1.1.0 was released. Here are some of the core improvements that were made to VASA 1.1.0.
- Significant improvement to the performance of Bind and Unbind requests
- Optimized processing batched bind and unbind requests
- Optimized the overall bind request and virtual volume query operations
- Optimized the handling of Replication Group Queries and simplified the response back to vSphere
- An increase in overall resources for VASA to communicate to the FlashArray's backend database service
- Increased the amount of task threads VASA has to the database service
- Increased the maximum amount of connections that VASA has to the database service
- Optimized the Managed Snapshot deletion process to take less time to complete
- Improved the VASA service's management of memory to address VASA OOM's
- Pure identified VASA processes to optimize memory usage and stop causing Out of Memory events in VASA
Just how much has the performance improved with Purity 5.3.6 and VASA 1.1.0 compared to previous versions of Purity and VASA? Great question, here are a couple of examples.