The VASA service pressure points on the FlashArray of concern would be how VASA is able to handle incoming requests, forward those requests to DB, receive the responses from DB and then send the responses back to vSphere.
- VASA processing incoming VASA Ops from the vSphere environment
- In the event that all of the hosts and vCenters connected to VASA are all sending as many VASA Ops as they can, the VASA service could be receiving between tens to thousands of requests at once. The more requests being issued to VASA at once will increase the amount of time that VASA is able to process those requests.
- VASA forwarding the Ops to the FlashArray DB Service
- There are differing levels to how complex a VASA op can be and depending on the operation, there can be multiple REST Requests that are forwarded to the Database service. For example, running an SPBM Replication Group Failover will forward many REST requests to the DB Service for just one VASA Op.
- VASA processing the response from the FlashArray DB Service
- There are instances where there are several responses from the DB service that VASA then needs to process and construct as a SOAP response to the issuer of the VASA Op.
- VASA sending the responses back to the vSphere environment
- Any impact here is generally related to the connectivity between VASA and the issuer, either network related or session authentication related.