Table of Contents

Search

  1. Preface
  2. Performance Tuning Overview
  3. Bottlenecks
  4. Optimizing the Target
  5. Optimizing the Source
  6. Optimizing Mappings
  7. Optimizing Transformations
  8. Optimizing Sessions
  9. Optimizing Grid Deployments
  10. Optimizing the PowerCenter Components
  11. Optimizing the System
  12. Using Pipeline Partitions
  13. Performance Counters

Performance Tuning Guide

Performance Tuning Guide

Object Caching for the Repository Service

Object Caching for the Repository Service

Repository object caching increases performance when you run workflows. When the Repository Service caches objects in memory, the Integration Service can more easily access the cached objects it needs to complete the workflow run.
To manage object caching for the Repository Service, configure the following properties:
Property
Description
Repository Agent Caching
Optional. Enables the repository agent caching, which improves the performance when the Integration Service runs multiple sessions repeatedly. If you enable this property, the Repository Service process caches metadata requested by the Integration Service and the metadata that describes repository objects. Default is Yes.
Agent Cache Capacity
Optional. Number of objects that the cache can contain when repository agent caching is enabled. You can increase the number of objects if there is available memory on the machine where the Repository Service process runs. Default is 10,000.
Allow Writes With Agent Caching
Optional. Allows you to use PowerCenter Client tools to change metadata in the repository when repository agent caching is enabled. When you enable writes, the Repository Service flushes the cache each time you save metadata through the PowerCenter Client. If you disable writes, you cannot save metadata to the repository through the PowerCenter Client, and the cache is not flushed. When you disable writes, the Integration Service can still write session and workflow metadata to the repository. The Repository Service does not flush the cache when the Integration Service writes metadata. Default is Yes.