企業管理 > 實行 Windchill ESI > Implementing Windchill ESI in an ORACLE Applications Environment > Performance Planning > Windchill ESI’s Performance-Related Design Concepts
  
Windchill ESI’s Performance-Related Design Concepts
This section highlights and lists aspects of Windchill ESI’s design that may impact performance. Taking these into consideration would be useful as you assess and plan for optimal performance.
Windchill ESI uses TIBCO Rendezvous Certified Messaging (RVCM), and therefore has the inherent performance overhead of managing ledger files. RVCM is required when interfacing to Oracle Applications to ensure robust transaction management.
Windchill ESI uses checkpoints at key points in the TIBCO BusinessWorks processing flow to prevent data corruption in the event of system failures. Checkpoints persist the current state of the application to disk, and therefore are notably slower to execute than memory-based operations. However, the location of checkpoints has been strategically designed to ensure robust transaction integrity while minimizing adverse performance effects.
Windchill ESI does not use an external or third-party database and therefore is not subjected to any of the associated performance impacts.
Windchill ESI does not support multi-threading (parallel processing) within a single transaction that publishes product data to a given destination (that is within a single BusinessWorks job). This is due, in part, to the object processing sequence required by Oracle Applications.