Home > Storage > PowerScale (Isilon) > Product Documentation > Storage (general) > Dell PowerScale: Common AntiVirus Agent Solution > Scenario 3: Performance impact on metadata read/write
In this scenario, we included the following subscenarios to better understand the performance impact from the CAVA workload:
Note: For comparison, all four subscenarios use the same requested operation rate that is configured in the workload benchmark tool.
Figure 14 shows the results of the achieved operations per second in the four subscenarios defined in the previous sections. The standard scanning profile, or if we exclude the workload path from the CAVA configuration, has almost no performance impact compared with the baseline result. The standard profile implements scan-on-close, which means that any file newly written or modified is submitted for virus scanning in the background after it is closed by the client. Scan-on-close is not synchronous in the host I/O path, and it slows down the incoming workload. In this case, the incoming workload proceeds unabated.
For the strict profile, the performance drops by 34%. This is because the strict profile adds scan-on-read. Any file not previously scanned, when opened for read by a client, is submitted for scanning at that time and it is synchronously in the host I/O path.
Figure 15 shows the average latency in the four subscenarios defined in the previous sections. The standard scanning profile, or if we exclude the workload path from the CAVA configuration, has almost the same latency compared with the baseline. In the strict profile, the latency increases by 52%.