<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: IOUG Day 2</title>
	<atom:link href="http://jonathanlewis.wordpress.com/2009/05/06/ioug-day-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://jonathanlewis.wordpress.com/2009/05/06/ioug-day-2/</link>
	<description>Just another Oracle weblog</description>
	<lastBuildDate>Mon, 20 May 2013 17:10:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jonathan Lewis</title>
		<link>http://jonathanlewis.wordpress.com/2009/05/06/ioug-day-2/#comment-33181</link>
		<dc:creator><![CDATA[Jonathan Lewis]]></dc:creator>
		<pubDate>Thu, 28 May 2009 22:25:18 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/?p=1130#comment-33181</guid>
		<description><![CDATA[Cristian,

Sorry I missed this note when it was first posted. It would be worth knowing what sort of speeds you are talking about.

One of the &quot;problems&quot; with increasing numbers of nodes is that you have an increased chance that you have to split a large &quot;read&quot; request into multiple 3-way transfers. 

When you compare this with the extreme case that you can get from a SAN (where SAN readahead pre-caches the next big multiblock read you&#039;re going to ask for) it&#039;s not too surprising that big tablescans can slow down. 

You have to remember that the important comparison should be between &quot;real disk&quot; speed and &quot;shared cache&quot; speed - but SANs often &quot;cheat&quot; on tablescans.]]></description>
		<content:encoded><![CDATA[<p>Cristian,</p>
<p>Sorry I missed this note when it was first posted. It would be worth knowing what sort of speeds you are talking about.</p>
<p>One of the &#8220;problems&#8221; with increasing numbers of nodes is that you have an increased chance that you have to split a large &#8220;read&#8221; request into multiple 3-way transfers. </p>
<p>When you compare this with the extreme case that you can get from a SAN (where SAN readahead pre-caches the next big multiblock read you&#8217;re going to ask for) it&#8217;s not too surprising that big tablescans can slow down. </p>
<p>You have to remember that the important comparison should be between &#8220;real disk&#8221; speed and &#8220;shared cache&#8221; speed &#8211; but SANs often &#8220;cheat&#8221; on tablescans.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cristian</title>
		<link>http://jonathanlewis.wordpress.com/2009/05/06/ioug-day-2/#comment-32917</link>
		<dc:creator><![CDATA[Cristian]]></dc:creator>
		<pubDate>Thu, 07 May 2009 08:04:56 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/?p=1130#comment-32917</guid>
		<description><![CDATA[Hi Jonathan,
there is a problem with the link in &quot;the oracle RAC SIG&quot;. But i want take this chance to say that with a four nodes RAC 10.2.0.4 we have encountered performance problems due to the fact that in full table scans getting blocks by global cache from remote nodes is sometimes a lot slower than getting them from disks. (a lot of &quot;gc cr multiblock request&quot; wait events) a we have found no hardware o interconnect communication probles.]]></description>
		<content:encoded><![CDATA[<p>Hi Jonathan,<br />
there is a problem with the link in &#8220;the oracle RAC SIG&#8221;. But i want take this chance to say that with a four nodes RAC 10.2.0.4 we have encountered performance problems due to the fact that in full table scans getting blocks by global cache from remote nodes is sometimes a lot slower than getting them from disks. (a lot of &#8220;gc cr multiblock request&#8221; wait events) a we have found no hardware o interconnect communication probles.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
