<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.6.5" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Aligning ASM Disks on Linux</title>
	<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux</link>
	<description>News and views from Pythian DBAs</description>
	<pubDate>Fri,  5 Dec 2008 03:28:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Ben M.</title>
		<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-299072</link>
		<dc:creator>Ben M.</dc:creator>
		<pubDate>Wed, 12 Nov 2008 17:04:20 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-299072</guid>
		<description>Great post indeed! Very hard to find information about this topic.

An other great page is the following:
http://insights.oetiker.ch/linux/raidoptimization.html

What would be great is a complete post on how to optimize the whole thing... 

HW RAID -&#62; Partitioning -&#62; LVM -&#62; File system option (Ext3 like stride, fs-type largefile4, etc)

About the following:

 &#62; Essentially, I “waste” 16 MBs, but gain aligned
 &#62; I/O for stripe width of up to 16 MB."

Based on the following page, I suspect "stripe width" isn't rightly used here...

"Stripe width refers to the number of parallel stripes that can be written to or read from simultaneously. This is of course equal to the number of disks in the array."

http://www.storagereview.com/guide2000/ref/hdd/perf/raid/concepts/perfStripe.html</description>
		<content:encoded><![CDATA[<p>Great post indeed! Very hard to find information about this topic.</p>
<p>An other great page is the following:<br />
<a href="http://insights.oetiker.ch/linux/raidoptimization.html" rel="nofollow">http://insights.oetiker.ch/linux/raidoptimization.html</a></p>
<p>What would be great is a complete post on how to optimize the whole thing&#8230; </p>
<p>HW RAID -&gt; Partitioning -&gt; LVM -&gt; File system option (Ext3 like stride, fs-type largefile4, etc)</p>
<p>About the following:</p>
<p> &gt; Essentially, I “waste” 16 MBs, but gain aligned<br />
 &gt; I/O for stripe width of up to 16 MB.&#8221;</p>
<p>Based on the following page, I suspect &#8220;stripe width&#8221; isn&#8217;t rightly used here&#8230;</p>
<p>&#8220;Stripe width refers to the number of parallel stripes that can be written to or read from simultaneously. This is of course equal to the number of disks in the array.&#8221;</p>
<p><a href="http://www.storagereview.com/guide2000/ref/hdd/perf/raid/concepts/perfStripe.html" rel="nofollow">http://www.storagereview.com/guide2000/ref/hdd/perf/raid/concepts/perfStripe.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hai Wu</title>
		<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-48151</link>
		<dc:creator>Hai Wu</dc:creator>
		<pubDate>Wed, 09 May 2007 23:11:04 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-48151</guid>
		<description>Ok. thanks for the confirmation. I will go with 2048 (1mb) then.</description>
		<content:encoded><![CDATA[<p>Ok. thanks for the confirmation. I will go with 2048 (1mb) then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Edwards</title>
		<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-48054</link>
		<dc:creator>David Edwards</dc:creator>
		<pubDate>Wed, 09 May 2007 18:43:02 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-48054</guid>
		<description>[Editorial Note: Christo pointed out that the sidebar on this page was getting pushed to the very bottom in IE browsers.  The culprit was the long raw URL in the first comment (by LSC).  To fix it, I edited the comment, condensing the URL into the words "this paper from Oracle".  The rest of that comment is untouched.]</description>
		<content:encoded><![CDATA[<p>[Editorial Note: Christo pointed out that the sidebar on this page was getting pushed to the very bottom in IE browsers.  The culprit was the long raw URL in the first comment (by LSC).  To fix it, I edited the comment, condensing the URL into the words &#8220;this paper from Oracle&#8221;.  The rest of that comment is untouched.]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christo Kutrovsky</title>
		<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-48042</link>
		<dc:creator>Christo Kutrovsky</dc:creator>
		<pubDate>Wed, 09 May 2007 17:36:29 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-48042</guid>
		<description>It's all good. However, consider this. ASM does it's allocations in 1mb "blocks". I wouldn't go under 1mb.

However, given what I know so far, 256k will be fine. Remembe we're talking about saving ~760 kb here ...</description>
		<content:encoded><![CDATA[<p>It&#8217;s all good. However, consider this. ASM does it&#8217;s allocations in 1mb &#8220;blocks&#8221;. I wouldn&#8217;t go under 1mb.</p>
<p>However, given what I know so far, 256k will be fine. Remembe we&#8217;re talking about saving ~760 kb here &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hai Wu</title>
		<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-48014</link>
		<dc:creator>Hai Wu</dc:creator>
		<pubDate>Wed, 09 May 2007 16:00:38 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-48014</guid>
		<description>Thanks Christo. Since we aren't going to get any stripe size that would be different from 128KB in this case, I guess I could configure the first sector to be 256 (128K) instead of 32768 (16M), so that it would do alignment for 128K stripe size. Do you see any issues in doing this?
Thanks,
Hai</description>
		<content:encoded><![CDATA[<p>Thanks Christo. Since we aren&#8217;t going to get any stripe size that would be different from 128KB in this case, I guess I could configure the first sector to be 256 (128K) instead of 32768 (16M), so that it would do alignment for 128K stripe size. Do you see any issues in doing this?<br />
Thanks,<br />
Hai</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christo Kutrovsky</title>
		<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-47981</link>
		<dc:creator>Christo Kutrovsky</dc:creator>
		<pubDate>Wed, 09 May 2007 14:25:54 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-47981</guid>
		<description>Yes it is. Because the default is a not a multiple of your stripe size. As long as it is a multiple of your stripe size you are good.

So if you offset at the 16th Mb as I do, then you will be alligned for all stripe sizes that are a power of 2, up to 16 Mb stripe size.

Now EMC has these hypervolumes that have the weird stripe sizes of 960 kb, that completelly destroys any allignement attempts :)</description>
		<content:encoded><![CDATA[<p>Yes it is. Because the default is a not a multiple of your stripe size. As long as it is a multiple of your stripe size you are good.</p>
<p>So if you offset at the 16th Mb as I do, then you will be alligned for all stripe sizes that are a power of 2, up to 16 Mb stripe size.</p>
<p>Now EMC has these hypervolumes that have the weird stripe sizes of 960 kb, that completelly destroys any allignement attempts :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hai Wu</title>
		<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-47785</link>
		<dc:creator>Hai Wu</dc:creator>
		<pubDate>Wed, 09 May 2007 03:09:33 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-47785</guid>
		<description>Hi Christo,
I was told by SAN administrators here that there's no way to change the stripe size for EMC LUN to be 1MB here, since it has already been set to 128KB for a big chunk of RAID5, every LUN will come from that one. 

In this case, there's no choice but to accept that as a fact. Is it necessary to do alignment as above for 128KB stripe size? 

Thanks,
Hai</description>
		<content:encoded><![CDATA[<p>Hi Christo,<br />
I was told by SAN administrators here that there&#8217;s no way to change the stripe size for EMC LUN to be 1MB here, since it has already been set to 128KB for a big chunk of RAID5, every LUN will come from that one. </p>
<p>In this case, there&#8217;s no choice but to accept that as a fact. Is it necessary to do alignment as above for 128KB stripe size? </p>
<p>Thanks,<br />
Hai</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christo Kutrovsky</title>
		<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-36296</link>
		<dc:creator>Christo Kutrovsky</dc:creator>
		<pubDate>Wed, 11 Apr 2007 13:26:22 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-36296</guid>
		<description>Hi Gustavo,

The aligning has to do with the RAID level stripe size, not with the ASM stripe size.

There's always a "penalty" on miss-aligned IO. You are using 2 devices, when you could have used only 1. Note, that using multiple devices is not bad by itself. What's bad is reading small amounts of data from multiple devices, as opposed to just 1.

You generally want to be doing at least 512kb io sizes per IO device, to achieve 90% of it's sequencial read speed (in my testing).</description>
		<content:encoded><![CDATA[<p>Hi Gustavo,</p>
<p>The aligning has to do with the RAID level stripe size, not with the ASM stripe size.</p>
<p>There&#8217;s always a &#8220;penalty&#8221; on miss-aligned IO. You are using 2 devices, when you could have used only 1. Note, that using multiple devices is not bad by itself. What&#8217;s bad is reading small amounts of data from multiple devices, as opposed to just 1.</p>
<p>You generally want to be doing at least 512kb io sizes per IO device, to achieve 90% of it&#8217;s sequencial read speed (in my testing).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gustavo Tamaki</title>
		<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-36239</link>
		<dc:creator>Gustavo Tamaki</dc:creator>
		<pubDate>Wed, 11 Apr 2007 09:52:20 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-36239</guid>
		<description>Hi Christo,

In your example, with a stripe size of 64KB, the number of unaligned I/Os are about 12.5%. If I consider the ASM stripe size of 1MB, can I assume that this number would drop to less than 1%? 

For a storage configured in RAID-10, the effect would be negligible, since the unalignment occurs only in the stripe boundaries and there's no right penalty, correct? 

Gustavo</description>
		<content:encoded><![CDATA[<p>Hi Christo,</p>
<p>In your example, with a stripe size of 64KB, the number of unaligned I/Os are about 12.5%. If I consider the ASM stripe size of 1MB, can I assume that this number would drop to less than 1%? </p>
<p>For a storage configured in RAID-10, the effect would be negligible, since the unalignment occurs only in the stripe boundaries and there&#8217;s no right penalty, correct? </p>
<p>Gustavo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christo Kutrovsky</title>
		<link>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-33096</link>
		<dc:creator>Christo Kutrovsky</dc:creator>
		<pubDate>Mon, 02 Apr 2007 00:22:35 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/411/aligning-asm-disks-on-linux#comment-33096</guid>
		<description>Yes it does mention it for solaris. 

The aligment applies to any OS. I must point out, that the default partitions in linux are worst case for alignment.</description>
		<content:encoded><![CDATA[<p>Yes it does mention it for solaris. </p>
<p>The aligment applies to any OS. I must point out, that the default partitions in linux are worst case for alignment.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
