RE: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- From: VIVEK_SHARMA <VIVEK_SHARMA@xxxxxxxxxxx>
- To: Christian Antognini <Christian.Antognini@xxxxxxxxxxxx>
- Date: Sun, 17 Feb 2008 12:38:21 +0530
Thanks Chris, folks
In the Benchmark Run for Batch processes, Setting "_write_clones" to "0" in
init.ora severely affected the performance Adversely & was removed thereafter.
Cause of the "latch: cache buffers chains" is believed to be "INSERT into IDT
Table" as this SQL appears on TOP in the section of the "ordered by gets" of
the Statspack Report.
The IDT Table has 64 HASH partitions partitioned on field Account(A/c) Number.
This is a Bank Accounts Interest processing Program & 1 Record gets inserted
per Account into IDT Table per Run. Since Account Number is unique per account,
could the INSERTs with different A/c Numbers still be accessing the SAME Block?
Any Other ideas? ... Will share the Statspack Report, if needed.
Cheers
Vivek
________________________________________
From: Christian Antognini [Christian.Antognini@xxxxxxxxxxxx]
Sent: Friday, February 15, 2008 1:42 PM
Vivek
> How is the "latch: cache buffers chains" wait to be addressed?
Has for any problem, you should start by understanding what is causing
it.
First of all you should find out which statements are experiencing it.
Then, you have to determine if the contention is due to inefficient
execution plans or simply because they are accessing the very same set
of blocks (there might be other causes... but this two are the most
frequent).
Since it is a benchmark, I would not exclude that the benchmark itself
is flawed. E.g. executing the very same SQL statement over and over
again...
> Should "_write_clones" be set to "0"
Why do you think so?
HTH
Chris
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are
not to copy, disclose, or distribute this e-mail or its contents to any other
person and any such actions are unlawful. This e-mail may contain viruses.
Infosys has taken every reasonable precaution to minimize this risk, but is not
liable for any damage you may sustain as a result of any virus in this e-mail.
You should carry out your own virus checks before opening the e-mail or
attachment. Infosys reserves the right to monitor and review the content of all
messages sent to or from this e-mail address. Messages sent to or from this
e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
--
http://www.freelists.org/webpage/oracle-l
- Follow-Ups:
- Re: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- From: Jonathan Lewis
Other related posts:
- » "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- » Re: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- » Re: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- » Re: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- » RE: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- » Re: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- » RE: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- » Re: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- » Re: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- Re: "latch: cache buffers chains" wait in NON-RAC Benchmark Runs
- From: Jonathan Lewis