<?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/"
		>
<channel>
	<title>Comments on: Testing FusionIO: strict_sync is too strict&#8230;</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/</link>
	<description>Everything about MySQL Performance</description>
	<lastBuildDate>Sat, 21 Nov 2009 05:23:57 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sumeet Bansal</title>
		<link>http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/comment-page-1/#comment-676717</link>
		<dc:creator>Sumeet Bansal</dc:creator>
		<pubDate>Fri, 13 Nov 2009 18:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=703#comment-676717</guid>
		<description>Hello Vadim,

I am the Principal Solutions Architect at Fusion-io.  I focus on Database systems integration with Fusion-io.

We have made some improvements in our latest drives that allow us to flush in-flight data.  Your feedback is very crucial for us and I would like to enlist your help in re-testing our product without strict_sync and simulating power loss scenarios to ascertain that there is no corruption or data loss.  If you are willing to something like this, please email me at sumeet@fusionio.com

Thanks.

regards,

Sumeet</description>
		<content:encoded><![CDATA[<p>Hello Vadim,</p>
<p>I am the Principal Solutions Architect at Fusion-io.  I focus on Database systems integration with Fusion-io.</p>
<p>We have made some improvements in our latest drives that allow us to flush in-flight data.  Your feedback is very crucial for us and I would like to enlist your help in re-testing our product without strict_sync and simulating power loss scenarios to ascertain that there is no corruption or data loss.  If you are willing to something like this, please email me at <a href="mailto:sumeet@fusionio.com">sumeet@fusionio.com</a></p>
<p>Thanks.</p>
<p>regards,</p>
<p>Sumeet</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadim</title>
		<link>http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/comment-page-1/#comment-588872</link>
		<dc:creator>Vadim</dc:creator>
		<pubDate>Thu, 18 Jun 2009 16:14:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=703#comment-588872</guid>
		<description>Stephan,

It&#039;s would be amazing if we will be able to rely on fsync without strict_sync and with the same performance!

I am testing tpcc-like benchmark. You can see more details about setup in this post.
http://www.mysqlperformanceblog.com/2009/04/30/looking-on-54-io-bound-benchmarks/

In this benchmark  I use 32 connection to mysql, but mysql settings are
innodb_write_io_threads=16
innodb_read_io_threads=16

so final concurrency on device may be different.


Please let me know when strict_sync is not be needed, I will re-test it.

Currently we can&#039;t recommend FusionIO to customers who have strong durability requirements.</description>
		<content:encoded><![CDATA[<p>Stephan,</p>
<p>It&#8217;s would be amazing if we will be able to rely on fsync without strict_sync and with the same performance!</p>
<p>I am testing tpcc-like benchmark. You can see more details about setup in this post.<br />
<a href="http://www.mysqlperformanceblog.com/2009/04/30/looking-on-54-io-bound-benchmarks/" rel="nofollow">http://www.mysqlperformanceblog.com/2009/04/30/looking-on-54-io-bound-benchmarks/</a></p>
<p>In this benchmark  I use 32 connection to mysql, but mysql settings are<br />
innodb_write_io_threads=16<br />
innodb_read_io_threads=16</p>
<p>so final concurrency on device may be different.</p>
<p>Please let me know when strict_sync is not be needed, I will re-test it.</p>
<p>Currently we can&#8217;t recommend FusionIO to customers who have strong durability requirements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephan Uphoff</title>
		<link>http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/comment-page-1/#comment-588844</link>
		<dc:creator>Stephan Uphoff</dc:creator>
		<pubDate>Thu, 18 Jun 2009 14:01:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=703#comment-588844</guid>
		<description>Vadim,

I expect that our next release will no longer require the strict_sync setting for durability (without any performance loss)
I am surprised about the low throughput - with or without strict_sync - are you testing with a single thread ? (Even for that it seems to be very slow)
Can you describe your test setup?

Currently with strict_sync on I recommend writing large blocks using at least two threads for writing (unless they are serialized by a file lock anyway).
For strict-sync you can think of the sync writes as participating in group commits that are either triggered by reaching a certain combined size (depending on card - should be smaller than 128K in your case) or a timeout.
Unfortunately the last write that reaches the combined &quot;group commit&quot; size will overflow into the next &quot;group commit&quot;.

Hope this helps and again - strict_sync should no longer be required in the near future.

Stephan</description>
		<content:encoded><![CDATA[<p>Vadim,</p>
<p>I expect that our next release will no longer require the strict_sync setting for durability (without any performance loss)<br />
I am surprised about the low throughput &#8211; with or without strict_sync &#8211; are you testing with a single thread ? (Even for that it seems to be very slow)<br />
Can you describe your test setup?</p>
<p>Currently with strict_sync on I recommend writing large blocks using at least two threads for writing (unless they are serialized by a file lock anyway).<br />
For strict-sync you can think of the sync writes as participating in group commits that are either triggered by reaching a certain combined size (depending on card &#8211; should be smaller than 128K in your case) or a timeout.<br />
Unfortunately the last write that reaches the combined &#8220;group commit&#8221; size will overflow into the next &#8220;group commit&#8221;.</p>
<p>Hope this helps and again &#8211; strict_sync should no longer be required in the near future.</p>
<p>Stephan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/comment-page-1/#comment-588297</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Wed, 17 Jun 2009 22:07:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=703#comment-588297</guid>
		<description>Didier Spezia,

This also surprises me.  $500 RAID cards have BBU on them.  I think it should not cost more than $100 to provide BBU  and same as for RAID card it should be possible to have it as an option but neither FusionIO nor any SSDs I know provide is an an option. 

Probably lying is good enough for most of users :)</description>
		<content:encoded><![CDATA[<p>Didier Spezia,</p>
<p>This also surprises me.  $500 RAID cards have BBU on them.  I think it should not cost more than $100 to provide BBU  and same as for RAID card it should be possible to have it as an option but neither FusionIO nor any SSDs I know provide is an an option. </p>
<p>Probably lying is good enough for most of users <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadim</title>
		<link>http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/comment-page-1/#comment-588198</link>
		<dc:creator>Vadim</dc:creator>
		<pubDate>Wed, 17 Jun 2009 18:44:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=703#comment-588198</guid>
		<description>Andy,

Mark may have used absolutely different setting for InnoDB and benchmarks, so results are not comparable in any way.</description>
		<content:encoded><![CDATA[<p>Andy,</p>
<p>Mark may have used absolutely different setting for InnoDB and benchmarks, so results are not comparable in any way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/comment-page-1/#comment-587918</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 17 Jun 2009 10:36:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=703#comment-587918</guid>
		<description>The tpm does look unbelievably low.

According to this benchmark:
http://mysqlha.blogspot.com/2009/06/innodb-io-bound-oltp-2-disk-server.html
A lowly PC with 2 SATA disk running software RAID 0 is getting around 3,000 tpm in tpcc-mysql.

That&#039;s more than what you got using FusionIO.

So a $10K FusionIO capable of 100K IOPS is outperformed by two $50 SATA drives in SW RAID 0???

Something&#039;s not right.</description>
		<content:encoded><![CDATA[<p>The tpm does look unbelievably low.</p>
<p>According to this benchmark:<br />
<a href="http://mysqlha.blogspot.com/2009/06/innodb-io-bound-oltp-2-disk-server.html" rel="nofollow">http://mysqlha.blogspot.com/2009/06/innodb-io-bound-oltp-2-disk-server.html</a><br />
A lowly PC with 2 SATA disk running software RAID 0 is getting around 3,000 tpm in tpcc-mysql.</p>
<p>That&#8217;s more than what you got using FusionIO.</p>
<p>So a $10K FusionIO capable of 100K IOPS is outperformed by two $50 SATA drives in SW RAID 0???</p>
<p>Something&#8217;s not right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrea</title>
		<link>http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/comment-page-1/#comment-587066</link>
		<dc:creator>Andrea</dc:creator>
		<pubDate>Tue, 16 Jun 2009 13:31:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=703#comment-587066</guid>
		<description>unbelievably low number of tpm!</description>
		<content:encoded><![CDATA[<p>unbelievably low number of tpm!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Didier Spezia</title>
		<link>http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/comment-page-1/#comment-587015</link>
		<dc:creator>Didier Spezia</dc:creator>
		<pubDate>Tue, 16 Jun 2009 12:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=703#comment-587015</guid>
		<description>A pity they do not provide an optional BBU for this kind of hardware ...</description>
		<content:encoded><![CDATA[<p>A pity they do not provide an optional BBU for this kind of hardware &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
