<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: btrfs 0.13 and XFS benchmarks</title>
	<atom:link href="http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/feed" rel="self" type="application/rss+xml" />
	<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks</link>
	<description>Computers, science, archaeology and other random burblings</description>
	<lastBuildDate>Tue, 20 Jul 2010 11:18:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: HOWTO - Kubuntu 9.04, RAID-10, LVM2, and XFS&#8230; &#171; Linux Free Trade Zone</title>
		<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/comment-page-1#comment-55386</link>
		<dc:creator>HOWTO - Kubuntu 9.04, RAID-10, LVM2, and XFS&#8230; &#171; Linux Free Trade Zone</dc:creator>
		<pubDate>Thu, 30 Apr 2009 17:35:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/?p=1116#comment-55386</guid>
		<description>[...] Links: http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks http://oss.oracle.com/projects/btrfs/dist/documentation/benchmark.html [...]</description>
		<content:encoded><![CDATA[<p>[...] Links: <a href="http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks" rel="nofollow">http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks</a> <a href="http://oss.oracle.com/projects/btrfs/dist/documentation/benchmark.html" rel="nofollow">http://oss.oracle.com/projects/btrfs/dist/documentation/benchmark.html</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bonnie++ Results for XFS on Dell E4200 SSD &#171; The Musings of Chris Samuel</title>
		<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/comment-page-1#comment-52463</link>
		<dc:creator>Bonnie++ Results for XFS on Dell E4200 SSD &#171; The Musings of Chris Samuel</dc:creator>
		<pubDate>Sat, 29 Nov 2008 12:16:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/?p=1116#comment-52463</guid>
		<description>[...] comparing with some old results on my home desktop system seems to show that the block I/O numbers are better, but the file manipulation stuff is much worse! [...]</description>
		<content:encoded><![CDATA[<p>[...] comparing with some old results on my home desktop system seems to show that the block I/O numbers are better, but the file manipulation stuff is much worse! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: petchema</title>
		<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/comment-page-1#comment-37970</link>
		<dc:creator>petchema</dc:creator>
		<pubDate>Tue, 17 Jun 2008 06:50:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/?p=1116#comment-37970</guid>
		<description>Until it becomes the default, it can be worth tweaking XFS parameters to improve the speed of metadata operations. Quick test on my workstation (Linux 2.6.25.4, 2GB ram):

# mkfs.xfs -f 
# mount -t xfs  
# bonnie++ -u nobody

Version 1.03c       ------Sequential Output------ --Sequential Input- --Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
attale           4G 10871  29 10931   2  8050   3 23348  61 37155   4 134.3   0
                    ------Sequential Create------ --------Random Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
                 16   646   3 +++++ +++   660   2   655   3 +++++ +++   319   1
attale.agematis.loc,4G,10871,29,10931,2,8050,3,23348,61,37155,4,134.3,0,16,646,3,+++++,+++,660,2,655,3,+++++,+++,319,1


# mkfs.xfs -f -l lazy-count=1,version=2,size=128m -i attr=2 -d agcount=4 
# mount -o logbsize=256k,nobarrier  
# bonnie++ -u nobody

Version 1.03c       ------Sequential Output------ --Sequential Input- --Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
attale           4G 11028  30 10690   2  8091   3 18795  48 34657   4 132.3   0
                    ------Sequential Create------ --------Random Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
                 16  1011   4 +++++ +++   707   2  1093   4 +++++ +++   526   2
attale,4G,11028,30,10690,2,8091,3,18795,48,34657,4,132.3,0,16,1011,4,+++++,+++,707,2,1093,4,+++++,+++,526,2</description>
		<content:encoded><![CDATA[<p>Until it becomes the default, it can be worth tweaking XFS parameters to improve the speed of metadata operations. Quick test on my workstation (Linux 2.6.25.4, 2GB ram):</p>
<p># mkfs.xfs -f<br />
# mount -t xfs<br />
# bonnie++ -u nobody</p>
<p>Version 1.03c       &#8212;&#8212;Sequential Output&#8212;&#8212; &#8211;Sequential Input- &#8211;Random-<br />
                    -Per Chr- &#8211;Block&#8211; -Rewrite- -Per Chr- &#8211;Block&#8211; &#8211;Seeks&#8211;<br />
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP<br />
attale           4G 10871  29 10931   2  8050   3 23348  61 37155   4 134.3   0<br />
                    &#8212;&#8212;Sequential Create&#8212;&#8212; &#8212;&#8212;&#8211;Random Create&#8212;&#8212;&#8211;<br />
                    -Create&#8211; &#8211;Read&#8212; -Delete&#8211; -Create&#8211; &#8211;Read&#8212; -Delete&#8211;<br />
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP<br />
                 16   646   3 +++++ +++   660   2   655   3 +++++ +++   319   1<br />
attale.agematis.loc,4G,10871,29,10931,2,8050,3,23348,61,37155,4,134.3,0,16,646,3,+++++,+++,660,2,655,3,+++++,+++,319,1</p>
<p># mkfs.xfs -f -l lazy-count=1,version=2,size=128m -i attr=2 -d agcount=4<br />
# mount -o logbsize=256k,nobarrier<br />
# bonnie++ -u nobody</p>
<p>Version 1.03c       &#8212;&#8212;Sequential Output&#8212;&#8212; &#8211;Sequential Input- &#8211;Random-<br />
                    -Per Chr- &#8211;Block&#8211; -Rewrite- -Per Chr- &#8211;Block&#8211; &#8211;Seeks&#8211;<br />
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP<br />
attale           4G 11028  30 10690   2  8091   3 18795  48 34657   4 132.3   0<br />
                    &#8212;&#8212;Sequential Create&#8212;&#8212; &#8212;&#8212;&#8211;Random Create&#8212;&#8212;&#8211;<br />
                    -Create&#8211; &#8211;Read&#8212; -Delete&#8211; -Create&#8211; &#8211;Read&#8212; -Delete&#8211;<br />
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP<br />
                 16  1011   4 +++++ +++   707   2  1093   4 +++++ +++   526   2<br />
attale,4G,11028,30,10690,2,8091,3,18795,48,34657,4,132.3,0,16,1011,4,+++++,+++,707,2,1093,4,+++++,+++,526,2</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Musings of Chris Samuel &#187; Blog Archive &#187; ZFS-FUSE Bonnie++ benchmark update</title>
		<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/comment-page-1#comment-19061</link>
		<dc:creator>The Musings of Chris Samuel &#187; Blog Archive &#187; ZFS-FUSE Bonnie++ benchmark update</dc:creator>
		<pubDate>Mon, 24 Mar 2008 11:49:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/?p=1116#comment-19061</guid>
		<description>[...] Chris Samuel: Juice, that&#8217;s fine, my point is that (as is a general rule in computing) the only benchmark that... [...]</description>
		<content:encoded><![CDATA[<p>[...] Chris Samuel: Juice, that&#8217;s fine, my point is that (as is a general rule in computing) the only benchmark that&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Samuel</title>
		<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/comment-page-1#comment-19048</link>
		<dc:creator>Chris Samuel</dc:creator>
		<pubDate>Mon, 24 Mar 2008 04:33:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/?p=1116#comment-19048</guid>
		<description>Juice, that&#039;s fine, my point is that (as is a general rule in computing) the only benchmark that really matters is your workload.

For the sort of workload I was testing the results were different, but that&#039;s just to be expected.  If we were testing a video streaming system it&#039;d be different again! ;-)</description>
		<content:encoded><![CDATA[<p>Juice, that&#8217;s fine, my point is that (as is a general rule in computing) the only benchmark that really matters is your workload.</p>
<p>For the sort of workload I was testing the results were different, but that&#8217;s just to be expected.  If we were testing a video streaming system it&#8217;d be different again! <img src='http://www.csamuel.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russell Coker</title>
		<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/comment-page-1#comment-19041</link>
		<dc:creator>Russell Coker</dc:creator>
		<pubDate>Mon, 24 Mar 2008 02:22:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/?p=1116#comment-19041</guid>
		<description>Most people don&#039;t even try to get 100,000 sub-directories.  Either hash the names or use the first character or two for names so that there are multiple levels of directory.  The way Squid stores it&#039;s files is an example of how to work around such bottlenecks.</description>
		<content:encoded><![CDATA[<p>Most people don&#8217;t even try to get 100,000 sub-directories.  Either hash the names or use the first character or two for names so that there are multiple levels of directory.  The way Squid stores it&#8217;s files is an example of how to work around such bottlenecks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: juice</title>
		<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/comment-page-1#comment-19036</link>
		<dc:creator>juice</dc:creator>
		<pubDate>Mon, 24 Mar 2008 01:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/?p=1116#comment-19036</guid>
		<description>i don&#039;t know, reiser4 was extremly fast for me, it was used as users partition only, files usually 10-100KB size. but it was not stable, i had few kernel oopses, and it was not worth it.

XFS was slow for metadata, and operating on a dir with 100 000 subdirs was so slow, that it was just crazy.

reiserfs is like 20-30% faster , talking about real life example, not tests. i personally think, that ext4 would be even faster than reiserfs, but i didn&#039;t dare to make users data partion on still dev fs.

so when considering only stable FSes, i can only say that reiserfs is faster than xfs (xfs tweaked, meaning like 8 different options mkfs/mount time) , on real life example, when there are many small files and many directories.

big files - i&#039;m sure XFS would blew away reiserfs easly, but i don&#039;t need it.</description>
		<content:encoded><![CDATA[<p>i don&#8217;t know, reiser4 was extremly fast for me, it was used as users partition only, files usually 10-100KB size. but it was not stable, i had few kernel oopses, and it was not worth it.</p>
<p>XFS was slow for metadata, and operating on a dir with 100 000 subdirs was so slow, that it was just crazy.</p>
<p>reiserfs is like 20-30% faster , talking about real life example, not tests. i personally think, that ext4 would be even faster than reiserfs, but i didn&#8217;t dare to make users data partion on still dev fs.</p>
<p>so when considering only stable FSes, i can only say that reiserfs is faster than xfs (xfs tweaked, meaning like 8 different options mkfs/mount time) , on real life example, when there are many small files and many directories.</p>
<p>big files &#8211; i&#8217;m sure XFS would blew away reiserfs easly, but i don&#8217;t need it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russell Coker</title>
		<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/comment-page-1#comment-19035</link>
		<dc:creator>Russell Coker</dc:creator>
		<pubDate>Mon, 24 Mar 2008 01:14:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/?p=1116#comment-19035</guid>
		<description>The XFS developers do a lot of regression testing at the high-end.  XFS doesn&#039;t look as good on a simple benchmark as it may do when you have some unusual high load situation in real life.

If you consider the value of your time and the value of uptime vs the cost of more disks then XFS starts to look a little more attractive too.</description>
		<content:encoded><![CDATA[<p>The XFS developers do a lot of regression testing at the high-end.  XFS doesn&#8217;t look as good on a simple benchmark as it may do when you have some unusual high load situation in real life.</p>
<p>If you consider the value of your time and the value of uptime vs the cost of more disks then XFS starts to look a little more attractive too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Samuel</title>
		<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/comment-page-1#comment-19034</link>
		<dc:creator>Chris Samuel</dc:creator>
		<pubDate>Mon, 24 Mar 2008 01:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/?p=1116#comment-19034</guid>
		<description>Forgot to mention - in the &lt;a href=&quot;http://www.csamuel.org/articles/emerging-filesystems-200709/#id2537430&quot;&gt;benchmarking I did&lt;/a&gt; Reiser4 (when it didn&#039;t crash the box) was slower than ReiserFS and both ext3 and ext4 were faster than both the Reiser filesystems for the workload I was using.

It&#039;s horses for courses, people should test their workload and pick whichever works best for them!</description>
		<content:encoded><![CDATA[<p>Forgot to mention &#8211; in the <a href="http://www.csamuel.org/articles/emerging-filesystems-200709/#id2537430">benchmarking I did</a> Reiser4 (when it didn&#8217;t crash the box) was slower than ReiserFS and both ext3 and ext4 were faster than both the Reiser filesystems for the workload I was using.</p>
<p>It&#8217;s horses for courses, people should test their workload and pick whichever works best for them!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Samuel</title>
		<link>http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks/comment-page-1#comment-19033</link>
		<dc:creator>Chris Samuel</dc:creator>
		<pubDate>Mon, 24 Mar 2008 01:05:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/?p=1116#comment-19033</guid>
		<description>Whilst I did use ReiserFS in the past (prior to ext3 arriving) I&#039;ve not used it for a long time - I don&#039;t really have a lot of confidence in it.</description>
		<content:encoded><![CDATA[<p>Whilst I did use ReiserFS in the past (prior to ext3 arriving) I&#8217;ve not used it for a long time &#8211; I don&#8217;t really have a lot of confidence in it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
