Performance Hit When Saving or Deploying Policies Parent topic

When adding, modifying, or deploying a HTTP or FTP Scan policy, there may be a few-second lag in that service while the update takes place. The actual duration of the lag varies depending on system hardware (CPU speed, single dual, or quad CPU, memory, etc.)
The typical sequence for updating a policy is, add or modify it and click Save, and then click Deploy. Both the Save action, and the Deploy action can trigger a temporary pause in scanning.
To minimize this impact, Trend Micro recommends that you add, modify, and/or deploy a new policy during low traffic times. For example, before starting a work day, at noon, or after normal working hours.
  • Note
    Note
    If you do not manually deploy a policy, it will be automatically updated as per the time interval that policy indicated on the IWSVA > Administration > IWSVA Configuration > Policy Deployment page under Policy Deployment Settings (in Minutes).