The FlashArray has a core service, called Purity OS that is running on the FlashArray. Part of this core service is to handle all incoming SAN requests as well as API requests. Factors that could impact Purity from handling these requests include, but are not limited to, are as follows:
- Overall high load on the FlashArray (Load Meter)
- At higher levels of overall load on the FlashArray, there will be less resources that VASA and the Database service will have to make requests to Purity. Additionally, Purity may take longer to process the requests issued from the DB Service.
- High front end IO workload and/or a High API workload
- Purity will always prioritize front end IO requests, so if there is a high amount of front end workload that is also causing high load on the array, then the Core Service is going to take longer to process the requests from the DB Service.