<?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>Don&#039;t Panic - Jeroen Baert&#039;s Blog &#187; performance</title>
	<atom:link href="http://forceflow.ulyssis.be/tag/performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://forceflow.ulyssis.be</link>
	<description>It&#039;s too late for the government to train me as a secret weapon.</description>
	<lastBuildDate>Sat, 31 Jul 2010 01:10:10 +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>VBO Win</title>
		<link>http://forceflow.ulyssis.be/2010/04/12/vbo-win/</link>
		<comments>http://forceflow.ulyssis.be/2010/04/12/vbo-win/#comments</comments>
		<pubDate>Mon, 12 Apr 2010 18:42:26 +0000</pubDate>
		<dc:creator>Jeroen</dc:creator>
				<category><![CDATA[en]]></category>
		<category><![CDATA[thesis]]></category>
		<category><![CDATA[c++]]></category>
		<category><![CDATA[glsl]]></category>
		<category><![CDATA[opengl]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[shaders]]></category>

		<guid isPermaLink="false">http://forceflow.ulyssis.be/?p=1298</guid>
		<description><![CDATA[Using Vertex Buffer Objects to transfer my mesh data (vertices, normals, curvatures) directly into GPU memory using STATIC_DRAW_ARB pointers just tripled the performance of my GLSL shader implementation. Running a heavy model (+300k vertices) drawn with contours and suggestive contours at 24 fps, average.]]></description>
		<wfw:commentRss>http://forceflow.ulyssis.be/2010/04/12/vbo-win/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Borderlands is a sloppy console port</title>
		<link>http://forceflow.ulyssis.be/2010/01/10/why-borderlands-is-a-sloppy-console-port/</link>
		<comments>http://forceflow.ulyssis.be/2010/01/10/why-borderlands-is-a-sloppy-console-port/#comments</comments>
		<pubDate>Sun, 10 Jan 2010 13:51:50 +0000</pubDate>
		<dc:creator>Jeroen</dc:creator>
				<category><![CDATA[en]]></category>
		<category><![CDATA[borderlands]]></category>
		<category><![CDATA[games]]></category>
		<category><![CDATA[graphics]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://forceflow.ulyssis.be/?p=939</guid>
		<description><![CDATA[A couple of weeks ago I purchased Borderlands, but only recently I found some time to install and run it. The hours that followed were a frustrating journey into performance issues, bad port quality and a first-hand experience on how having consoles as a primary market, in the end, backfires on us all. Loading up <a href='http://forceflow.ulyssis.be/2010/01/10/why-borderlands-is-a-sloppy-console-port/'>[...]</a>]]></description>
		<wfw:commentRss>http://forceflow.ulyssis.be/2010/01/10/why-borderlands-is-a-sloppy-console-port/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Jaunty Intel Performance Fix (update)</title>
		<link>http://forceflow.ulyssis.be/2009/06/05/jaunty-intel-performance-fix-update/</link>
		<comments>http://forceflow.ulyssis.be/2009/06/05/jaunty-intel-performance-fix-update/#comments</comments>
		<pubDate>Fri, 05 Jun 2009 15:39:09 +0000</pubDate>
		<dc:creator>Jeroen</dc:creator>
				<category><![CDATA[en]]></category>
		<category><![CDATA[graphics]]></category>
		<category><![CDATA[intel]]></category>
		<category><![CDATA[jaunty]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://forceflow.ulyssis.be/?p=523</guid>
		<description><![CDATA[A couple of weeks ago, I reported about a fix for Intel driver performance regression in Ubuntu 9.04 (Jaunty Jackalope). The fix solved the overal responsiveness of the interface (especially for composite-enabled desktops), but introduced a new problem which wasn&#8217;t visible at first: a memory leak slowly filling up swap space. Over the course of <a href='http://forceflow.ulyssis.be/2009/06/05/jaunty-intel-performance-fix-update/'>[...]</a>]]></description>
		<wfw:commentRss>http://forceflow.ulyssis.be/2009/06/05/jaunty-intel-performance-fix-update/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Jaunty Intel Performance Fix</title>
		<link>http://forceflow.ulyssis.be/2009/05/09/ubuntu-jaunty-intel-fix/</link>
		<comments>http://forceflow.ulyssis.be/2009/05/09/ubuntu-jaunty-intel-fix/#comments</comments>
		<pubDate>Sat, 09 May 2009 22:29:23 +0000</pubDate>
		<dc:creator>Jeroen</dc:creator>
				<category><![CDATA[en]]></category>
		<category><![CDATA[intel]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://forceflow.ulyssis.be/?p=505</guid>
		<description><![CDATA[After upgrading from Intrepid (8.10) to Jaunty (9.04) I noticed a noticeable performance hit, in 2d and 3d applications on my Ubuntu system, running a (rather crappy) Intel 945GM mobile graphics chip. After poking around on the Ubuntu forums I found this thread. The problem seems to be the switch between EXA and UXA in <a href='http://forceflow.ulyssis.be/2009/05/09/ubuntu-jaunty-intel-fix/'>[...]</a>]]></description>
		<wfw:commentRss>http://forceflow.ulyssis.be/2009/05/09/ubuntu-jaunty-intel-fix/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
