CPU usage is low to medium, depending on the volume of change data that is being captured and that is being read.

I/O rates vary, depending on the volume of change data that is being captured and that is being read.

Virtual memory usage varies, depending on the number and size of the PowerExchange Logger active log data sets.

For the IMS synchronous ECCR, CICS/VSAM ECCR, and Batch VSAM ECCR, the PowerExchange Logger must be assigned to a service class that the same priority as the processes that perform the changes (that is, the IMS region, CICS region, or address space of the batch job) or that has a higher priority than these processes. If the PowerExchange Logger uses a lower priority, it might delay the processes. For more information, see Monitoring the PowerExchange Logger for z/OS.

For the log-based ECCRS that capture change data from online database log files asynchronously, the PowerExchange Logger performance requirements depend on your extraction requirements.

If you run PowerCenter Real Time CDC sessions that use continuous extraction mode and need to deliver captured change data to the target with minimum latency, assign the PowerExchange Logger and the database processes that perform the changes to the same service class. With this service class configuration, the PowerExchange Logger can keep up with these database processes.
If you run PowerCenter CDC sessions that extract change data in batch mode from either PowerExchange Logger log files or from condense files, assign the PowerExchange Logger to a service class that is used by batch jobs.