"gc current block busy" wait in Concurrent BATCH Processes Run

From: VIVEK_SHARMA <VIVEK_SHARMA_at_infosys.com>
Date: Wed, 13 Feb 2008 22:24:37 +0530
Message-ID: <69E1360E54B50C4A828A136C158E4742036A70775A@BLRKECMBX02.ad.infosys.com>


In a Benchmark Run, 256 concurrent BATCH Processes on RAC using Dedicated Sessions (NON-MTS) showing the following Waits:-

How is the "gc current block busy" wait to be addressed? From the Statspack Report (Level 7) which section gives the Objects which is incurring this wait? Is it the "Segments By Current Blocks Received" section OR the "Segments by CR Blocks Received" section?

Will share the Statspack Report, as needed.

Oracle on 3 Node RAC
Solaris 10



Statspack Report's Time Elapsed: 11.97 (mins)

Top 5 Timed Events                                                 Avg    %Total

~~~~~~~~~~~~~~~~~~                                                 wait    Call

Event                                     Waits        Time (s)    (ms)    Time

----------------------------------------- ------------ ----------- ------ ------
CPU time 5,854 57.6 gc current block busy 24,910 1,463 59 14.4 SQL*Net break/reset to client 1,075,218 1,285 1 12.6 gcs log flush sync 103,520 511 5 5.0 gc buffer busy 6,489 367 57 3.6

Host CPU (CPUs: 120)

~~~~~~~~ Load Average

Begin End User System Idle WIO WCPU

  • ------- ------- ------- ------- ------- --------

8.58 9.54

          8.26 15.61 76.13 0.00 1.19

  • 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***
Received on Wed Feb 13 2008 - 10:54:37 CST

Original text of this message