Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> Responses to Vivek Sharma's multiple postings on Oracle-L
Dear Vivek,
I totally respect your "requests for clarification" and I will be more than happy to give them to you. But going forward, I urge you NOT to send "specific questions" on bullet points in the powerpoint slides of my presentations to the list (and that too multiple times), instead send it to me directly at - gajav_at_yahoo.com.
Your questions "directed to me" but posted on the list may not be appropriate for the following reasons:
Here are responses to your queries:
Ans. For most storage architectures available today,
an average service time for I/O requests that exceeds
20ms is considered a "bottleneck". Service times of
20ms or above are usually accompanied by "wait queue
and run queue" numbers that are non-zero. What is
"high" for one environment, may not be relevant for
another. The 20ms threshold may not be applicable to
some of the more esoteric storage devices (such as
solid state disks). These are "guidelines" NOT
"draconian rules".
2) sar -d Interpretation. "%busy can be high if service times are within (4 *CPU time-slice)". What does CPU time-slice mean & how can it be Calculated ?
Ans. The "4*CPU time-slice" guideline is a method we used in the past to diagnose I/O bottlenecks. I mention this to "lay some foundation and history" during my presentation.
For example, if your system's CPU timeslice was set at
10ms, any service time above 40ms was considered to be
"high". CPU time slice is the amount of CPU time a
process gets when requesting the CPU, until it
consumes the slice, or undergoes a context switch to
perform I/O. The CPU timeslice is a OS kernel
configurable parameter. Please check your OS docs for
specific details. Again, a guideline NOT a rule.
3) How to configure sort_write_buffers and sort_write_buffer_size?
Ans. These parameters are configured (prior to Oracle8i) to enable Oracle to write the temporary segments directly to disk, by bypassing the database buffer cache. This is only relevant when configuring SORT_DIRECT_WRITES to TRUE. The 2 related parameters namely SORT_WRITE_BUFFERS and SORT_WRITE_BUFFER_SIZE can be set to 4 and 65536 (but the max. values for these may be OS dependent). From Oracle 8.1 onwards, the only configurable sort parameters are SORT_AREA_SIZE, SORT_AREA_RETAINED_SIZE and SORT_MULTIBLOCK_READ_COUNT, as all other sort-related parameters have been de-supported.
Hope that helps,
Gaja
-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Gaja Krishna Vaidyanatha INET: oraperfman_at_yahoo.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).Received on Thu Jun 28 2001 - 14:42:57 CDT