<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6487.1">
<TITLE>[Ocfs-users] Follow up on async I/O question</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>
<P><FONT FACE="Times New Roman">Sunil Mushran wrote:</FONT>
<BR><FONT FACE="Times New Roman">>And as that gets into reading debugocfs outputs, the user has to make the determination, if the effort is worth the gain in performance. Why only logfiles? Well, because Oracle performs large ios only to the logfiles. The ios to be datafiles are in smaller chunks. Hope this helps. Sunil </FONT></P>
<BR>
<P><FONT SIZE=2 FACE="Arial">I'd like to point out a small mistake in this post. Oracle most certainly performs large IOs to more</FONT>
<BR><FONT SIZE=2 FACE="Arial">than just logfiles. Parallel Query and normal foreground processes alike perform multiblock IO.</FONT>
<BR><FONT SIZE=2 FACE="Arial">They are known as direct path read and write, scattered read and others and are driven by full scans,</FONT>
<BR><FONT SIZE=2 FACE="Arial">index range scans, foreground temp segment IO, recovery and so on.</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2 FACE="Arial">Kevin Closson</FONT>
<BR><FONT SIZE=2 FACE="Arial">Chief Architect, Database Solutions</FONT>
<BR><FONT SIZE=2 FACE="Arial">PolyServe, Inc</FONT>
</P>
</BODY>
</HTML>