One performance consideration is to identify the resource requirements, like CPU, memory, and so on that Data Validation Option mappings and sessions will require in each PowerCenter environment. Another consideration is to ensure that the additional load will not be a problem for either the environment or other users in that environment.

Data Validation Option, on its own, does not place any load on your PowerCenter environment. Instead, the load on PowerCenter depends on how many jobs are run, how much data is tested, the kind of tests run, how things are configured, what else is running on the server, and so on. As such, users themselves decide the load placed on the PowerCenter environment by defining and executing jobs with Data Validation Option.

The following include ways to optimize performance that are directly supported by Data Validation Option:

Sending WHERE clauses, counts, and aggregations into databases, where possible.
Having presorted data, where possible, as joins on presorted data are significantly faster than those on unsorted data.
Using data sampling (in database, if possible) to reduce the amount of data tested.