Академический Документы
Профессиональный Документы
Культура Документы
Within the scope of the RDBMS, Response Time in it’s simplest form consists of
Service Time + Wait Time. Service Time equates to time the request is actively
being processed on the CPU, while Wait Time encompasses everything else.
6.7
3.55
51.25
38.82
The chart depicts a breakdown of response time from March 1 8:00 AM – March
1 6:00 PM. During this period, an average of only 38% of response time was
CPU related. The remaining 62% of response time was spent waiting on various
resources. The remaining predominate wait events were db file sequential read,
db file scattered read, buffer busy waits, and async disk IO.
The db file sequential read event signifies a wait for an I/O read request to
complete. A sequential read is usually a singleblock read that is typically used
when reading indexes, although it is possible to see sequential reads for more
than one block. This call differs from "db file scattered read" in that a sequential
read reads data into contiguous memory (while a scattered read reads multiple
blocks and scatters them into different buffers in the SGA).
Resource Intensive SQL
Any effort of improving performance must involve reviewing the actual SQL code
that is submitted in transactions to determine if it can be optimized. The largest
performance improvements usually come from tuning the actual code, not from
adjusting database parameters. It is important to periodically extract the most
resource intensive SQL and examine it for improvement opportunities.
Statement
Identifier Statement Disk
Reads
A Program = Dcrtsora 14.5%
Others 75.20%
Statement
Identifier Statement Buffer Gets
Others 54.12%
Statement
Identifier Statement BuffGet/Execuation