RE: Solid State Disks for Databases

:-)  

V$SESSION_EVENT produces the same kind of problem.  

There are situations in which V$SESSION_EVENT can provide information that is even more misleading than what V$SYSTEM_EVENT shows. There's such an example in Figure 3-7 and Table 3-4 of Optimizing Oracle Performance.    

Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com <http://www.hotsos.com/> Nullius in verba

Visit www.hotsos.com <http://www.hotsos.com/> for curriculum and schedule details...  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Paul Baumgartel
Sent: Tuesday, September 27, 2005 12:29 PM To: Oracle-L
Subject: Re: Solid State Disks for Databases    

On 9/27/05, Cary Millsap <Cary.Millsap_at_hotsos.com> wrote:

The one idea I'd like to highlight...

Specifically, I'll mention that if V$SYSTEM_EVENT shows that I/O "wait events" have consumed more time than any other "wait event" (Statspack, for example), then you have no idea by how much SSD might help your end users' performance, or whether in fact SSD will even help at all.

Is the point here simply that the wait information in this view isn't broken down by session, as opposed to v$session_wait?
--

Paul Baumgartel
paul.baumgartel_at_aya.yale.edu

--

http://www.freelists.org/webpage/oracle-l Received on Tue Sep 27 2005 - 12:49:10 CDT