<?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: Comments on Phoronix Benchmarking openSUSE 11.1</title>
	<atom:link href="http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/feed/" rel="self" type="application/rss+xml" />
	<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/</link>
	<description>Blogs and Ramblings of the openSUSE Members</description>
	<lastBuildDate>Mon, 30 Jan 2012 19:11:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Rob</title>
		<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/#comment-707</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Wed, 04 Feb 2009 13:07:27 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=318#comment-707</guid>
		<description>Since I wrote this, I came across comments by Andrew Morton, and a thread discussing barriers and why he refused a patch to make them a default.  The sequential layout of journal, in general means the disk does the writes in right order, except when wrapping round (relatively rare); meaning in general running without barriers is a problem only for the unfortunate.
Other filesystems like XFS, may frequently corrupt disk data files on power-failure, so running with a UPS supporting ordered shutdown is advisable.
One performance issue in 11.1 may be due to CPUFREQ demand governor, having an overly long sample size (at least on AMD X2 with Cool N&#039; Quiet), I was informed this will be reduced in a kernel update.</description>
		<content:encoded><![CDATA[<p>Since I wrote this, I came across comments by Andrew Morton, and a thread discussing barriers and why he refused a patch to make them a default.  The sequential layout of journal, in general means the disk does the writes in right order, except when wrapping round (relatively rare); meaning in general running without barriers is a problem only for the unfortunate.<br />
Other filesystems like XFS, may frequently corrupt disk data files on power-failure, so running with a UPS supporting ordered shutdown is advisable.<br />
One performance issue in 11.1 may be due to CPUFREQ demand governor, having an overly long sample size (at least on AMD X2 with Cool N&#8217; Quiet), I was informed this will be reduced in a kernel update.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/#comment-706</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Wed, 04 Feb 2009 12:57:53 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=318#comment-706</guid>
		<description>I think it&#039;s XAA, as Intel developed changed to EXA as a default after the 11.0 release.</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s XAA, as Intel developed changed to EXA as a default after the 11.0 release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suzer Surya</title>
		<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/#comment-698</link>
		<dc:creator>Suzer Surya</dc:creator>
		<pubDate>Mon, 02 Feb 2009 18:54:06 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=318#comment-698</guid>
		<description>Some feedback for Andreas Jaeger; Firstly your Suse 11 release was solid and fast (I ran many benchmarks and your results were good). Especially the Intel driver + OpenGL + Compositing/Compiz as well KDE4; especially your binary of Firefox 3 (30% faster) blew away both Swiftfox and SwiftWeasel which were supposed to be optimized to my exact core2duo x84_64. BTW could you confirm whether Suse 11.0 Intel driver uses XAA or EXA accel by default. However, Suse 11.1 has turned out to be mixed bag; more bad than good I&#039;m afraid, especially the Intel Graphics performance, inconsistent repositories, missing apps for suse 11.1 repos, revision mismatches; clipper causing corruption in cut and paste  during editing openoffice  spreadsheets (corrupting production spreadsheets is a really bad thing) when using KDE4.1.3, wierd slowdowns with opensource radeon/radeonhd drivers, in ability even simple OpenGL apps like torcs to even launch (Segmentation Fault). The problems were such that I had to downgrade all our systems backdown to Suse 11.0 (which is fantastic, stable and consistent). With my systems back at Suse 11.0 - ZERO problems and really responsive desktops &amp; servers, back to fresh installing to Suse 11.1 and the problems mentioned, re-manifest (my install media are fine and md5sum just fine). I can&#039;t understand what happened with suse 11.1 after such a beautiful &amp; clean release of Suse 11.0. But these benchmarks that you are commenting on above do not surprise me in light of all the other stuff we experienced here with 11.1.
PS is Suse 11.0 Intel driver using XAA or EXA as a default?</description>
		<content:encoded><![CDATA[<p>Some feedback for Andreas Jaeger; Firstly your Suse 11 release was solid and fast (I ran many benchmarks and your results were good). Especially the Intel driver + OpenGL + Compositing/Compiz as well KDE4; especially your binary of Firefox 3 (30% faster) blew away both Swiftfox and SwiftWeasel which were supposed to be optimized to my exact core2duo x84_64. BTW could you confirm whether Suse 11.0 Intel driver uses XAA or EXA accel by default. However, Suse 11.1 has turned out to be mixed bag; more bad than good I&#8217;m afraid, especially the Intel Graphics performance, inconsistent repositories, missing apps for suse 11.1 repos, revision mismatches; clipper causing corruption in cut and paste  during editing openoffice  spreadsheets (corrupting production spreadsheets is a really bad thing) when using KDE4.1.3, wierd slowdowns with opensource radeon/radeonhd drivers, in ability even simple OpenGL apps like torcs to even launch (Segmentation Fault). The problems were such that I had to downgrade all our systems backdown to Suse 11.0 (which is fantastic, stable and consistent). With my systems back at Suse 11.0 &#8211; ZERO problems and really responsive desktops &amp; servers, back to fresh installing to Suse 11.1 and the problems mentioned, re-manifest (my install media are fine and md5sum just fine). I can&#8217;t understand what happened with suse 11.1 after such a beautiful &amp; clean release of Suse 11.0. But these benchmarks that you are commenting on above do not surprise me in light of all the other stuff we experienced here with 11.1.<br />
PS is Suse 11.0 Intel driver using XAA or EXA as a default?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave P</title>
		<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/#comment-570</link>
		<dc:creator>Dave P</dc:creator>
		<pubDate>Wed, 24 Dec 2008 07:56:32 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=318#comment-570</guid>
		<description>ext3&#039;s performance is visibly slower than either xfs or reiserfs and definitely +1 for the robustness of xfs with system crashes an sudden power outages. Opensuse needs to seriously consider making xfs the default file system.</description>
		<content:encoded><![CDATA[<p>ext3&#8242;s performance is visibly slower than either xfs or reiserfs and definitely +1 for the robustness of xfs with system crashes an sudden power outages. Opensuse needs to seriously consider making xfs the default file system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M. Edward (Ed) Borasky</title>
		<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/#comment-565</link>
		<dc:creator>M. Edward (Ed) Borasky</dc:creator>
		<pubDate>Sun, 21 Dec 2008 23:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=318#comment-565</guid>
		<description>If you want to do speed vs. safety tradeoffs on filesystems, you might as well do a *thorough* I/O subsystem tuning analysis, rather than just do half-assed benchmarks comparing community distros out of the box. If that stuff matters to you, you&#039;re going to be using hardware RAID with battery-backed caches, you&#039;re going to try all the filesystems under stress conditions, you&#039;re going to be careful about file and filesystem placement, etc. And if you&#039;re interested in high-speed graphics, you&#039;ll use proprietary drivers rather than the open-source ones anyway.</description>
		<content:encoded><![CDATA[<p>If you want to do speed vs. safety tradeoffs on filesystems, you might as well do a *thorough* I/O subsystem tuning analysis, rather than just do half-assed benchmarks comparing community distros out of the box. If that stuff matters to you, you&#8217;re going to be using hardware RAID with battery-backed caches, you&#8217;re going to try all the filesystems under stress conditions, you&#8217;re going to be careful about file and filesystem placement, etc. And if you&#8217;re interested in high-speed graphics, you&#8217;ll use proprietary drivers rather than the open-source ones anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Hilkewich</title>
		<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/#comment-561</link>
		<dc:creator>Dean Hilkewich</dc:creator>
		<pubDate>Sat, 20 Dec 2008 22:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=318#comment-561</guid>
		<description>Compiler optimizations are not the issue here.  The issue is easily replicated on various setups.The same slowness is observed on P3 / K7 / K8 / P4 / Core&#039;s / Phenoms / Xeons and is present in 32-bit and 64-bit flavors of openSUSE.</description>
		<content:encoded><![CDATA[<p>Compiler optimizations are not the issue here.  The issue is easily replicated on various setups.The same slowness is observed on P3 / K7 / K8 / P4 / Core&#8217;s / Phenoms / Xeons and is present in 32-bit and 64-bit flavors of openSUSE.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Jaeger</title>
		<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/#comment-549</link>
		<dc:creator>Andreas Jaeger</dc:creator>
		<pubDate>Thu, 18 Dec 2008 08:56:32 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=318#comment-549</guid>
		<description>Dan, thanks for the info.  That explains Mandriva&#039;s results.</description>
		<content:encoded><![CDATA[<p>Dan, thanks for the info.  That explains Mandriva&#8217;s results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan O'Brian</title>
		<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/#comment-545</link>
		<dc:creator>Dan O'Brian</dc:creator>
		<pubDate>Thu, 18 Dec 2008 01:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=318#comment-545</guid>
		<description>Andreas: I discovered this article via a link from Roy Schestowitz&#039;s attack on the performance of openSUSE using these benchmarks (I know, I know... what else is new, right?).

Anyhow, even though I am not an openSUSE user myself, I wanted to help you guys out and did a bit of research into your EXA vs XAA question and came up with the following link: http://www.nabble.com/-Cooker--ANN:-Acceleration-method-change-for-intel-driver-td20110862.html

It would appear that Mandriva was defaulting to XAA for Intel cards up until Oct 22nd, which was post release of Mandrake 10. It&#039;s probably safe to assume that Mandriva Linux in the benchmarks was defaulting to XAA.</description>
		<content:encoded><![CDATA[<p>Andreas: I discovered this article via a link from Roy Schestowitz&#8217;s attack on the performance of openSUSE using these benchmarks (I know, I know&#8230; what else is new, right?).</p>
<p>Anyhow, even though I am not an openSUSE user myself, I wanted to help you guys out and did a bit of research into your EXA vs XAA question and came up with the following link: <a href="http://www.nabble.com/-Cooker--ANN:-Acceleration-method-change-for-intel-driver-td20110862.html" rel="nofollow">http://www.nabble.com/-Cooker&#8211;ANN:-Acceleration-method-change-for-intel-driver-td20110862.html</a></p>
<p>It would appear that Mandriva was defaulting to XAA for Intel cards up until Oct 22nd, which was post release of Mandrake 10. It&#8217;s probably safe to assume that Mandriva Linux in the benchmarks was defaulting to XAA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 6205</title>
		<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/#comment-544</link>
		<dc:creator>6205</dc:creator>
		<pubDate>Wed, 17 Dec 2008 18:06:14 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=318#comment-544</guid>
		<description>Hmm...no, i was at that time without a pc :( Now i&#039;m waiting for GM hoping it will work OK, because it&#039;s better than Ubuntu in many ways, at least 11.0 was.</description>
		<content:encoded><![CDATA[<p>Hmm&#8230;no, i was at that time without a pc <img src='http://lizards.opensuse.org/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  Now i&#8217;m waiting for GM hoping it will work OK, because it&#8217;s better than Ubuntu in many ways, at least 11.0 was.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Jaeger</title>
		<link>http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/#comment-543</link>
		<dc:creator>Andreas Jaeger</dc:creator>
		<pubDate>Wed, 17 Dec 2008 14:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=318#comment-543</guid>
		<description>Compiler flags might play into it as well and could explain some noise.</description>
		<content:encoded><![CDATA[<p>Compiler flags might play into it as well and could explain some noise.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

