<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>eduardofleury.com &#187; QEdje</title>
	<atom:link href="http://blog.eduardofleury.com/archives/category/qedje/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.eduardofleury.com</link>
	<description>Thoughts, shuffled...</description>
	<lastBuildDate>Sat, 01 May 2010 00:22:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Improving QEdje and Qt performance with nvidia drivers.</title>
		<link>http://blog.eduardofleury.com/archives/2008/08/34/</link>
		<comments>http://blog.eduardofleury.com/archives/2008/08/34/#comments</comments>
		<pubDate>Thu, 21 Aug 2008 23:14:40 +0000</pubDate>
		<dc:creator>fleury</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Misc Links]]></category>
		<category><![CDATA[Primary]]></category>
		<category><![CDATA[QEdje]]></category>
		<category><![CDATA[Qt]]></category>
		<category><![CDATA[Qt Labs Americas (en)]]></category>
		<category><![CDATA[gentoo]]></category>
		<category><![CDATA[kde]]></category>
		<category><![CDATA[nvidia]]></category>
		<category><![CDATA[opengl]]></category>

		<guid isPermaLink="false">http://blog.eduardofleury.com/?p=34</guid>
		<description><![CDATA[Hey all, You may have been following the buzz around bad 2D performance of nvidia-drivers, specially with KDE 4. Well, I found out that QEdje was running slower than it could on my machine due to the same reason. Zack Rusin released yesterday a nice benchmark utility for Qt, QGears2, which I used to measure [...]]]></description>
			<content:encoded><![CDATA[<p>Hey all,</p>
<p>You may have been following the buzz around bad 2D performance of nvidia-drivers, specially with KDE 4. Well, I found out that QEdje was running slower than it could on my machine due to the same reason.</p>
<p>Zack Rusin released yesterday a nice benchmark utility for Qt, <a title="Zack Rusin blog - QGears2" href="http://zrusin.blogspot.com/2008/08/fast-graphics.html" target="_blank">QGears2</a>, which I used to measure the effect of <a title="Lemma's suggestion to improve nVidia 2D performance" href="http://techbase.kde.org/User:Lemma/KDE4-NVIDIA" target="_blank">Lemma&#8217;s suggestion on KDE&#8217;s techbase</a>.</p>
<p>My machine is a 2.4GHz Core 2 Duo / 2gb / nVidiaGeForce 8600M 256mb MacBook Pro, running Gentoo ~x86.</p>
<p>The first tests were conducted using:</p>
<ul>
<li>Xorg-server 1.4.2</li>
<li>Xorg 7.3</li>
<li>nvidia proprietary drivers (nvidia-drivers) 173.14.12</li>
</ul>
<p>The second test session were conducted after the following changes:</p>
<ul>
<li>nvidia proprietary drivers (nvidia-drivers) 177.67 beta (I&#8217;ve unmasked them in Gentoo)</li>
<li>Added PixmapCacheSize and OnDemandVBlankInterrupts options to xorg.conf</li>
<li>applied InitialPixmapPlacement and GlyphCache hacks:
<pre>nvidia-settings -a InitialPixmapPlacement=2 -a GlyphCache=1</pre>
</li>
</ul>
<p><strong>GEARSFANCY results</strong>:</p>
<p><strong>Old setup</strong>:</p>
<ul>
<li>-image  &#8211;&gt;  42 fps</li>
<li>-render &#8211;&gt; 35 fps</li>
<li>-gl &#8211;&gt; 396 fps</li>
</ul>
<p><strong>New setup</strong>:</p>
<ul>
<li>-image  &#8211;&gt;  67 fps</li>
<li>-render  &#8211;&gt;  41 fps</li>
<li>-gl  &#8211;&gt;  476 fps</li>
</ul>
<p>Let me know of your results.</p>
<p>Cheers,</p>
<p>Fleury</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.eduardofleury.com/archives/2008/08/34/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Running x11perf on Maemo (N800)</title>
		<link>http://blog.eduardofleury.com/archives/2008/08/29/</link>
		<comments>http://blog.eduardofleury.com/archives/2008/08/29/#comments</comments>
		<pubDate>Wed, 20 Aug 2008 03:25:14 +0000</pubDate>
		<dc:creator>fleury</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Maemo]]></category>
		<category><![CDATA[Primary]]></category>
		<category><![CDATA[QEdje]]></category>
		<category><![CDATA[Qt]]></category>
		<category><![CDATA[qt qedje maemo english linux]]></category>

		<guid isPermaLink="false">http://blog.eduardofleury.com/?p=29</guid>
		<description><![CDATA[Hi all, this post is about some benchmarks we did on Nokia&#8217;s N800 device to measure the performance of XShmPutImage on this hardware. I&#8217;ve been working on the QEdje project and, while studying possible optimizations, our team was interested in measuring whether we could benefit from using MIT&#8217;s X11 shared memory extensions. Among other tests, [...]]]></description>
			<content:encoded><![CDATA[<p>Hi all, this post is about some benchmarks we did on Nokia&#8217;s N800 device to measure the performance of XShmPutImage on this hardware.</p>
<p>I&#8217;ve been working on the QEdje project and, while studying possible optimizations, our team was interested in measuring whether we could benefit from using MIT&#8217;s X11 shared memory extensions. Among other tests, I managed to run x11perf on the N800.</p>
<p>A simple patch was needed before cross-compiling it. This because this app has a hard-coded window size of 600&#215;600 pixels, more than what&#8217;s available in our 800&#215;480 screen, thus leading to a X error message, complaining about get screen parameters.</p>
<p>I also reduced the square side size from 500 to 400 pixels in the XShmPutImage and XPutImage tests (<em>shmput500</em> and <em>putimage500</em>).</p>
<p>The results were absolutely favorable to the use of the shared memory extension as you can see below:</p>
<p>./x11perf -<strong>shmput500</strong> -sync</p>
<p>800 reps @   8.6566 msec (   <strong>116.0/sec</strong>)</p>
<p>./x11perf <strong>-putimage500</strong> -sync</p>
<p>360 reps @  14.8336 msec (    <strong>67.4/sec</strong>)</p>
<p>For those willing to reproduce the tests, the patch is available below and should apply cleanly to x11perf 1.5.</p>
<p><a title="x11perf 1.5 patch" href="http://blog.eduardofleury.com/wp-content/uploads/x11perf-1.5-maemo.patch" target="_self">Download x11perf 1.5 patch</a></p>
<p>Cheers,</p>
<p>Fleury</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.eduardofleury.com/archives/2008/08/29/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
