Database Reference
In-Depth Information
CPU spikes
Application server(s) running the Oracle SOA Suite can experience the CPU spikes
for one of the following reason(s):
•
User activity
: The sudden peak in the user(s) requests can cause CPU
spikes on the application server(s). The key is to understand the user
types and their pay load and performance needs. For example, users
sending individual real time transaction demands that these transactions
are completed in the shortest possible time while batch and cron users
won't mind waiting for the transactions to finish successfully. It is a leading
practice to build separate platforms for serving real time end users and
batch and cron users.
•
Request queuing
: The real spikes in the users' requests can also be
caused by the CPU spikes that result in poor performance. You may plan
to adjust your system architecture to avoid the queuing of users' requests
by adding more application server(s).
•
Thread count
: High thread count setting in a server platform can cause
CPU spikes as well. Identify an optimal setting for the thread count so that
your server platform can handle it.
•
External processes
:Sometimes applicationbatchjobsrunningontheap-
plication server can cause CPU spikes as well. You may have often no-
ticed that backup, anti-virus, and logs compression task also causes the
CPU spikes on the application server(s). Minimize these external tasks on
the application server(s) to avoid the CPU spikes.
