ProTip for VSE: Are exclusions hurting rather than helping your performance?

Version 1

    The On Access Scanner is very efficient in determining if a file should or should not be scanned. However, even excluding a file adds file I/O overhead to a file operation, and it’s therefore possible for your configured exclusions to bog down the OAS rather than help you. Exclusions are best used when:

    The file is known to be clean and does not get modified

    The file does get modified but the file name is constant

    The exclusion is specific to a single file only

    When pattern matching criteria is used, wildcard use is limited to a Start or Finish criteria, not both (for example, **\this.file is good but **\this*\** is not so good.)


    Beyond that, the sheer number of exclusions you have could be a hindrance. If the exclusion count on each node has broken the hundred count, consider revising the exclusions that are in place and confirm if they are really needed – and where they are needed, is an exclusion the best choice for solving the performance concern? Did you know there are alternate ways to improve performance? Find out more from the following sources:


    KB79589 — How to make On Access Scanner (real-time) exclusions more secure

    KB61143 — When to create exclusions by drive letter or device name

    KB54812 — How to use wildcards when creating exclusions in VirusScan Enterprise 8.x

    KB50998 — How to manage file and folder exclusions in VirusScan Enterprise 8.x using wildcards

    KB55139 — Understanding High-Risk, Low-Risk, and Default processes configuration and usage

    On Access Scanner - Improve Performance & Maintain Security