|Oracle® Complex Event Processing Developer's Guide
11g Release 1 (11.1.1) for Eclipse
Part Number E14301-03
This chapter describes techniques for increasing Oracle CEP server and application performance, including:
When creating high-availability applications for deployment to multi-server domains, consider the following performance tuning options:
For more information, see Section 16.3, "Designing an Oracle CEP Application for High Availability"
If you only want availability and are not concerned with recovery time, then it is possible to use smaller, less equipped hosts as secondaries. However, to maximize high availability performance, ensure that all hosts in the multi-server domain are identical: same number and type of processor, same quantity of memory, same number and size of disks.
The Oracle CEP high availability input adapter is applicable to all high availability quality of service options. However, because the high availability input adapter increases performance overhead, it is not appropriate for some high availability quality of service options (such as Section 16.2.1, "Simple Failover" and Section 16.2.2, "Simple Failover with Buffering").
If you are using application time from the event then you do not need to use the input adapter. Application time from the event is always preferable from a performance standpoint.
Consider increasing the
batch-size to reduce the amount of time the primary server spends broadcasting event messages and to reduce the amount of time the secondary servers spend processing these messages.
batch-size may increase the likelihood of missed and duplicate events if the primary fails before broadcasting an event message with a large number of events.
For more information, see Table 17-3 in Section 220.127.116.11, "High Availability Input Adapter Component Configuration File Configuration"
Consider decreasing the
trimming-interval to reduce the amount of time the primary server spends broadcasting trimming messages and to reduce the amount of time the secondary servers spend processing these messages.
trimming-interval may increase recovery time as the new primary server's in-memory queue will be more out of date relative to the old primary.
For more information, see Table 17-9 in Section 18.104.22.168, "Broadcast Output Adapter Component Configuration File Configuration".
When configuring Oracle Coherence in a high-availability architecture, consider the following performance tuning options:
For more information, see "Testing and Tuning" in the Oracle Coherence Developer's Guide.
To reduce failover time, increase Coherence heartbeat timeout machine frequency and reduce the number of heartbeats before failure.
Implement the Oracle Coherence "simple" serialization interface (not the one that requires XML registration).